Skip to content

Edge index planning in sync with variable start planner#2293

Merged
Ignition merged 54 commits intomasterfrom
edge-index-planning
Sep 16, 2024
Merged

Edge index planning in sync with variable start planner#2293
Ignition merged 54 commits intomasterfrom
edge-index-planning

Conversation

@Josipmrden
Copy link
Contributor

@Josipmrden Josipmrden commented Aug 27, 2024

Edge index planning made robust with the variable start planner like the node planning.
Before this PR, the plans could only be generated with scanning of nodes, followed by expansion. Since we introduced edge indices based on edge type and edge-property type, the planner needs to be adjusted so it can generate a scanning of indexed edge triplets (from, edge, to) in order to perform valid expansion.
If there is no edge index present, the plan will not be used, since we don't have a data structure that will iterate over all the edges and their triplets. That plan is invalid. All plans starting from an edge index are valid.

@Josipmrden Josipmrden added this to the mg-v2.20.0 milestone Sep 10, 2024
@Josipmrden Josipmrden marked this pull request as ready for review September 10, 2024 10:32
@sonarqubecloud
Copy link

@Ignition Ignition added this pull request to the merge queue Sep 16, 2024
Merged via the queue into master with commit 7d0cdf8 Sep 16, 2024
@Ignition Ignition deleted the edge-index-planning branch September 16, 2024 16:35
as51340 pushed a commit that referenced this pull request Oct 24, 2025
Edge index planning made robust with the variable start planner like the
node planning.
Before this PR, the plans could only be generated with scanning of
nodes, followed by expansion. Since we introduced edge indices based on
edge type and edge-property type, the planner needs to be adjusted so it
can generate a scanning of indexed edge triplets (from, edge, to) in
order to perform valid expansion.
If there is no edge index present, the plan will not be used, since we
don't have a data structure that will iterate over all the edges and
their triplets. That plan is invalid. All plans starting from an edge
index are valid.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI -build=community -test=core Run community build and core tests on push CI -build=coverage -test=core Run coverage build and core tests on push CI -build=debug -test=core Run debug build and core tests on push CI -build=debug -test=integration Run debug build and integration tests on push CI -build=jepsen -test=core Run jepsen build and core tests on push CI -build=release -test=benchmark Run release build and benchmark on push CI -build=release -test=core Run release build and core tests on push CI -build=release -test=e2e Run release build and e2e tests on push CI -build=release -test=stress Run release build and stress tests on push customer customer Docs needed Docs needed feature feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants