[gitbuda]

Documents linked vertices, new in MemGQL 0.15.0: the same entity declared once per connector with a shared linkKey, so a path crosses from one database into another at that node without an edge or a connector named in the query.

• Schema File: new section One vertex in several connectors (declaration, how a crossing runs, what a whole-node return looks like, naming rules for labels and keys, rules and limits), plus linkKey rows in the vertex field table and the glossary.
• Multiple Graphs: a pointer from Traversing across backends with an edge to linked vertices, for when both sides are the same entity.
• Reference: the shared-label limitation and the routing paragraph now say how a label several connectors carry is placed (relationship types, linkKey) and that the error names the connectors; the mapping section mentions linkKey.
• Memgraph: new Several Memgraph instances section — one connector per instance, routing by relationship type, a two-MATCH join that ships keys as an IN list, and the linkKey form.
• Amazon Redshift: new Joining Redshift with a graph section — a Redshift table as one home of a linked vertex, with keys sent to Redshift as bind parameters.
• Changelog (v0.15.0, unreleased): linked vertices; IN-list push-down for joins between connectors no graph maps; the clearer error when a label lives in several connectors of one graph.
• Reference → Supported GQL Query Features: rows for a path crossing at a linked vertex, a cross-connector edge and holding a vertex's content, with the connectors each was checked against.
• Schema File: a vertex's content may also live in MongoDB.
• Changelog: bug fix — content properties of a vertex that is not the first node of its pattern were returned null.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
documentation	Ready	Preview	Oct 28, 2026 4:39pm UTC