Skip to content

LanceDB Integration #2317

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

Closed

Conversation

parshvadaftari
Copy link
Contributor

Description

Add LanceDB as Vectorstore.

Fixes #2212

Type of change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)
  • Refactor (does not change functionality, e.g. code style improvements, linting)
  • Documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Please delete options that are not relevant.

  • Unit Test
  • Test Script

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have checked my code and corrected any misspellings

Maintainer Checklist

@parshvadaftari
Copy link
Contributor Author

@Dev-Khant I've runned the tests locally by make test command. The tests are failing here due to cached env and hence it's skipping the dependency installation which does not install the newer ones. Can you help me out here?

- `provider`: The name of the vector database (e.g., "chroma", "pgvector", "qdrant", "milvus","azure_ai_search", "vertex_ai_vector_search")
- `config`: A nested dictionary containing provider-specific settings

- `provider`: The name of the vector database (e.g., "chroma", "pgvector", "qdrant", "milvus", "azure_ai_search", "lance")

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- `provider`: The name of the vector database (e.g., "chroma", "pgvector", "qdrant", "milvus", "azure_ai_search", "lance")
- `provider`: The name of the vector database (e.g., "chroma", "pgvector", "qdrant", "milvus", "azure_ai_search", "vertex_ai_vector_search", "lance")

lancedb shouldn't replace vertex ai search

@EricAVigo
Copy link

Hi team, I'm interested in this LanceDB integration. What's the current status and is there anything I can do to help move it forward?

@parshvadaftari
Copy link
Contributor Author

Closing this PR, you can reference new updated PR for lancedb integration here -> #3018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support for LanceDB
3 participants