-
Notifications
You must be signed in to change notification settings - Fork 678
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: LanceDB Integration #1749
Conversation
Very basic LanceDB integration for table operations. synchronous only.
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.
Thanks @Benedikt-Wolf! Mind rebasing and fixing the merge conflict?
|
||
assert span.attributes.get(SpanAttributes.VECTOR_DB_VENDOR) == "lancedb" | ||
assert span.attributes.get(SpanAttributes.VECTOR_DB_OPERATION) == "add" | ||
assert span.attributes.get(SpanAttributes.MILVUS_INSERT_DATA_COUNT) == 2 |
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.
Hmm... We don't have a generic one for this? :(
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.
I don't think so right now, but I'd be happy to discuss how we can genericize VectorDB Operations without losing the small semantic differences between providers.
Very basic LanceDB integration for table operations. synchronous only.
#241
feat(instrumentation): ...
orfix(instrumentation): ...
.