Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement graph serialization / structure under Bolt protocol #2007

Open
gitbuda opened this issue May 5, 2024 · 0 comments
Open

Implement graph serialization / structure under Bolt protocol #2007

gitbuda opened this issue May 5, 2024 · 0 comments
Labels
customer customer Effort - High Effort - High Frequency - Monthly Frequency - Monthly Priority - Later Priority - Later Reach - VeryFew Reach - VeryFew Severity - S3 Severity - S3

Comments

@gitbuda
Copy link
Member

gitbuda commented May 5, 2024

https://neo4j.com/docs/bolt/current/bolt/structure-semantics/ -> the graph/subgraph is missing.

Equivalent to path, but encoding multiple "paths" essentially minimizing the network traffic because the user only needs info about the whole graph.

The question is, how does the engine know that it's ok to serialize something into a graph? Most likely, a Graph data type on the query engine side is enough (the user would have to "collect" vertices|edges|paths into a graph).

@gitbuda gitbuda added Effort - High Effort - High Severity - S3 Severity - S3 customer customer Frequency - Monthly Frequency - Monthly Reach - VeryFew Reach - VeryFew labels May 5, 2024
@hal-eisen-MG hal-eisen-MG added the Priority - Later Priority - Later label May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer customer Effort - High Effort - High Frequency - Monthly Frequency - Monthly Priority - Later Priority - Later Reach - VeryFew Reach - VeryFew Severity - S3 Severity - S3
Projects
None yet
Development

No branches or pull requests

2 participants