Skip to content

TINKERPOP-1143 Moved TraversalEngine to gremlin-test#830

Merged
asfgit merged 1 commit intomasterfrom
TINKERPOP-1143
Apr 16, 2018
Merged

TINKERPOP-1143 Moved TraversalEngine to gremlin-test#830
asfgit merged 1 commit intomasterfrom
TINKERPOP-1143

Conversation

@spmallette
Copy link
Contributor

https://issues.apache.org/jira/browse/TINKERPOP-1143

TraversalEngine and related infrastructure was deprecated way back on 3.2.0 but it was kept around because it was used in some infrastructure for testing. Graph providers should in no way still be using this interface and should have long ago gone to Computer as the gremlin-core infrastructure long ago quit using TraversalEngine in any capacity.

The only weird part was that MatchStep used TraversalEngine as a switch - I just converted that to use a boolean for checks that determine if the step is being executed onComputer or not.

All tests pass with docker/build.sh -t -n -i

VOTE +1

if (this.first) {
this.first = false;
this.initializeMatchAlgorithm(TraversalEngine.Type.STANDARD);
this.initializeMatchAlgorithm(true);
Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't this be false?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

oh wow - good catch. i guess the tests pass either way though...don't know if that's bad.???

Copy link
Contributor

Choose a reason for hiding this comment

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

It's not bad. I don't fully understand the code in CountMatchAlgorithm (the only place where the boolean flag makes a difference), but it seems like it only reorders the match traversals, possibly to optimize memory consumption and/or processing time.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

that makes sense - fixed and pushed

TraversalEngine and related infrastructure was deprecated way back on 3.2.0 but it was kept around because it was used in some infrastructure for testing. Graph providers should in no way still be using this interface and should have long ago gone to Computer as the gremlin-core infrastructure long ago quit using TraversalEngine in any capacity.
@dkuppitz
Copy link
Contributor

dkuppitz commented Apr 6, 2018

VOTE: +1

@robertdale
Copy link
Member

VOTE +1

@asfgit asfgit merged commit 11519d5 into master Apr 16, 2018
@asfgit asfgit deleted the TINKERPOP-1143 branch May 19, 2018 09:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants