mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-13 07:12:27 +00:00
Will JonesandClaude Opus 5.5
b1429ffa68
## Summary LanceDB's remote HTTP client (reqwest) and gRPC client (tonic) used rustls with the `ring` crypto provider, while the AWS SDK and object_store use aws-lc-rs. This moves both clients to aws-lc-rs: - `tonic`: `tls-ring` → `tls-aws-lc`. - `reqwest`: 0.12 → 0.13. reqwest 0.12 has no aws-lc-rs feature; 0.13's `rustls` feature uses it. 0.13 was already in the lockfile through object_store. No code changes were needed. - `macos-system-configuration` is replaced by its 0.13 name, `system-proxy`, which also reads the system proxy on Windows. - `query` is now an opt-in feature in 0.13; it's used for request query parameters. - Certificate verification moves from `rustls-native-certs` to `rustls-platform-verifier`, which uses the OS verifier on macOS and Windows. `ring` is still compiled in, because `lance-namespace-impls` and `lance-namespace-reqwest-client` enable it through reqwest 0.12 (lance-format/lance#9855, lance-format/lance-namespace#369). Both clients here pick aws-lc-rs explicitly, so they don't depend on which providers are compiled in. ## Evidence A temporary example that connects the remote client to real HTTPS hosts: ``` https://example.com: Http error: ... 404 Not Found: <!doctype html>... # TLS handshake OK https://expired.badssl.com: Hit retry limit ... connect_failures=3/3 # bad cert rejected ``` ## Merge Risk **Door:** two-way; dependency feature changes only. **Blast Radius:** `remote` TLS and certificate verification (Python, Node, and Rust LanceDB Cloud clients). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The Multimodal Lakehouse for AI
How to Install ✦ Detailed Documentation ✦ Tutorials and Recipes ✦ Contributors
The ultimate multimodal data platform for AI/ML applications.
LanceDB is designed for fast, scalable, and production-ready vector search. It is built on top of the Lance columnar format. You can store, index, and search over petabytes of multimodal data and vectors with ease. LanceDB is a central location where developers can build, train and analyze their AI workloads.
Demo: Multimodal Search by Keyword, Vector or with SQL
Star LanceDB to get updates!
⭐ Click here ⭐ to see how fast we're growing!
Key Features:
- Fast Vector Search: Search billions of vectors in milliseconds with state-of-the-art indexing.
- Comprehensive Search: Support for vector similarity search, full-text search and SQL.
- Multimodal Support: Store, query and filter vectors, metadata and multimodal data (text, images, videos, point clouds, and more).
- Advanced Features: Zero-copy, automatic versioning, manage versions of your data without needing extra infrastructure. GPU support in building vector index.
Products:
- Open Source & Local: 100% open source, runs locally or in your cloud. No vendor lock-in.
- Cloud and Enterprise: Production-scale vector search with no servers to manage. Complete data sovereignty and security.
Ecosystem:
- Columnar Storage: Built on the Lance columnar format for efficient storage and analytics.
- Seamless Integration: Python, Node.js, Rust, and REST APIs for easy integration. Native Python and Javascript/Typescript support.
- Rich Ecosystem: Integrations with LangChain 🦜️🔗, LlamaIndex 🦙, Apache-Arrow, Pandas, Polars, DuckDB and more on the way.
How to Install:
Follow the Quickstart doc to set up LanceDB locally.
API & SDK: We also support Python, Typescript and Rust SDKs
| Interface | Documentation |
|---|---|
| Python SDK | https://lancedb.github.io/lancedb/python/python/ |
| Typescript SDK | https://lancedb.github.io/lancedb/js/globals/ |
| Rust SDK | https://docs.rs/lancedb/latest/lancedb/index.html |
| REST API | https://docs.lancedb.com/api-reference/rest |
Join Us and Contribute
We welcome contributions from everyone! Whether you're a developer, researcher, or just someone who wants to help out.
If you have any suggestions or feature requests, please feel free to open an issue on GitHub or discuss it on our Discord server.
Check out the GitHub Issues if you would like to work on the features that are planned for the future. If you have any suggestions or feature requests, please feel free to open an issue on GitHub.
Contributors
Stay in Touch With Us