You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently no native driver support for Weaviate (https://weaviate.io/), an open-source AI-native vector database. Teams building semantic search, RAG, and other AI/ML workloads rely on Weaviate for vector storage and similarity search, but cannot connect it through TablePro today. This forces us to manage Weaviate separately from the other databases we already access through TablePro, which is slow and fragmented.
Proposed solution
Add native driver support for Weaviate (https://weaviate.io/) so it can be added and accessed alongside the other 18+ supported databases. Ideally this would include connecting via Weaviate's REST/gRPC endpoints (or its client APIs), browsing collections/classes, and running vector and hybrid search queries from within TablePro.
Alternatives considered
Considered managing Weaviate separately through its own console/clients (e.g., the Weaviate Python/JS clients or REST API directly), but this means context-switching out of TablePro and losing a unified workflow. Also considered using a generic HTTP/REST tool, but it lacks first-class schema browsing and query support for Weaviate collections.
Activity
J2TeamNNL commentedon Sep 11, 2026
PR that adds Weaviate as a registry REST plugin (collections as tables): J2TeamNNL#8
Upstream compare: main...J2TeamNNL:cursor/weaviate-rest-driver-c3a9
This is a fork PR. It will not close this issue until it is opened against TableProApp/TablePro. No plugin-weaviate-v* tag.
J2TeamNNL commentedon Sep 11, 2026
PR that adds Weaviate as a registry REST plugin (collections as tables): #2742