-
Notifications
You must be signed in to change notification settings - Fork 854
[3.9] Restrict hybrid disjoint sg directions for Path Queries #16333
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. 10000 We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…r is stored in a different number type.
…ybrid-disjoint-sg-directions
@@ -202,20 +253,27 @@ GraphNode::GraphNode(ExecutionPlan* plan, ExecutionNodeId id, | |||
THROW_ARANGO_EXCEPTION_MESSAGE(TRI_ERROR_ARANGO_COLLECTION_TYPE_INVALID, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The error message could be misleading if the collection cannot be found. Then we should rather return TRI_ERROR_ARANGO_DATA_SOURCE_NOT_FOUND and an appropriate message.
But I don't insist on making this change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree on this change.
However I think this independent of this PR (code here is old)
Will create followup pr for this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (only two open todos found).
(Side note: OptimizerRules are really hard to review)
Co-authored-by: Jan <jsteemann@users.noreply.github.com>
Scope & Purpose
Backport of #16214
This PR hits the enterprise version only.
For Hybrid Disjoint SmartGraphs we decided to restrict switches between Smart and Satellite
for a single AQL Node to at most one switch.
So every Graph node that switches two (or more) times will cause the query to reject.
Note: This is a breaking change! there can be queries that do not work anymore.
However original behavior especially for path queries, delivered undefined results.
Please see Enterprise PR for technical details.
Checklist
Related Information
(Please reference tickets / specification / other PRs etc)