feat(graph): Flexible Schema Extension to SpannerGraphStore #125
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Allow a dynamic schema for nodes and edges: - nodes are stored in one table with dynamic label and properties (JSON) - Allow more than one (src.node.id, target.node.id, edge.type) by introducing a uuid as part of the key; - Prefix the table names with graph names to avoid conflicting.
product-auto-label
bot
added
the
api: spanner
mtyin
changed the title
mtyin
changed the title
Previously, we override all columns by schema; with this change, we selectively write specified columns. Note: - this won't change the behavior if you always do a full blind write;
averikitsch
requested changes
Jan 25, 2025
averikitsch
reviewed
Feb 7, 2025
averikitsch
approved these changes
Feb 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat(graph): Extension to SpannerGraphStore
Many use cases don't have a clean pre-specified schema, hence this change adds support to generic flexible graph schema.
Fixes #<issue_number_goes_here> 🦕