-
-
Notifications
You must be signed in to change notification settings - Fork 3
Feature: Semantic schema search #32
Copy link
Copy link
Open
Labels
apiREST API or GraphQL relatedREST API or GraphQL relatedenhancementImprovement to existing functionalityImprovement to existing functionalityfeatureNew feature or functionalityNew feature or functionality
Description
Activity
Metadata
Metadata
Assignees
Labels
apiREST API or GraphQL relatedREST API or GraphQL relatedenhancementImprovement to existing functionalityImprovement to existing functionalityfeatureNew feature or functionalityNew feature or functionality
Problem Statement
Search/filtering in the graph visualization (Neovis.js) currently only matches on exact names. On older or inconsistently named databases (e.g.
inv_hdrinstead ofinvoices), users can't find relevant tables using natural language.Proposed Solution
EmbeddingProviderport and store them in the vector index.internal/interfaces/web/).Alternative Solutions
Full-text search (Neo4j Lucene index) — simpler, but won't capture semantic similarity without exact word matches.
Use Case
A user working with a large legacy schema can quickly find relevant tables/columns without knowing exact names.
Priority Level
Nice to have
Implementation Ideas
schema/schema.graphqlswith a new query type for semantic search.transformCLI command so normal runs aren't slowed down when AI is disabled.Additional Context
Depends on: "Native vector index foundation", "EmbeddingProvider port".