-
Notifications
You must be signed in to change notification settings - Fork 874
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add Vectara destination connector #2357
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
checking, was there any resolution on validation of the stored and embedded results?
actual should wait for response on "can we test the embedding results"
@ryannikolaidis I can make a post request with a text query. (but not an embedding) And then have it give the top example. We do get some metadata we can check for. But once the partitioned file hits Vectara, it is a black box. So no guarantee what the are doing as far as embeddings and search. Example of response: I looked for some other endpoints that might give us embedding information. But there wasn't anything I found useful. |
Ahh, I see. I think we could but we would need to build and hit the appropriate app in Vectara that also leverages the data we've written. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, I think checking count is good enough for now. It would be nice as a future enhancement to actually test end to end with a test application we build in Vectara, but this should at least given us confidence that we're writing to it.
Thanks to Ofer at Vectara, we now have a Vectara destination connector.