8000 [3.9] Restrict hybrid disjoint sg directions for Path Queries by mchacki · Pull Request #16333 · arangodb/arangodb · GitHub
[go: up one dir, main page]

Skip to content

[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

Merged
merged 8 commits into from
Jun 7, 2022

Conversation

mchacki
Copy link
Member
@mchacki mchacki commented May 25, 2022

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.

  • 💩 Bugfix
  • 🍕 New feature
  • 🔥 Performance improvement
  • 🔨 Refactoring/simplification

Checklist

  • Tests
    • Regression tests
    • C++ Unit tests
    • integration tests
    • resilience tests
  • 📖 CHANGELOG entry made
  • 📚 documentation written (release notes, API changes, ...)
  • Backports
    • Backport for 3.9: (Please link PR)
    • Backport for 3.8: (Please link PR)
    • Backport for 3.7: (Please link PR)

Related Information

(Please reference tickets / specification / other PRs etc)

@mchacki mchacki added the 1 Bug label May 25, 2022
@mchacki mchacki added this to the 3.9.2 milestone May 25, 2022
@mchacki mchacki self-assigned this May 25, 2022
@@ -202,20 +253,27 @@ GraphNode::GraphNode(ExecutionPlan* plan, ExecutionNodeId id,
THROW_ARANGO_EXCEPTION_MESSAGE(TRI_ERROR_ARANGO_COLLECTION_TYPE_INVALID,
Copy link
Contributor

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.

Copy link
Member Author

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.

Copy link
Contributor
@jsteemann jsteemann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member
@hkernbach hkernbach left a 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)

mchacki and others added 2 commits June 3, 2022 15:36
Co-authored-by: Jan <jsteemann@users.noreply.github.com>
@KVS85 KVS85 added the 3 Graph Graph query engine label Jun 3, 2022
@KVS85 KVS85 merged commit 56bb0f3 into 3.9 Jun 7, 2022
@KVS85 KVS85 deleted the bug-fix-3.9/restrict-hybrid-disjoint-sg-directions branch June 7, 2022 20:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 Bug 3 Graph Graph query engine
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0