GitHub user okram opened a pull request:
https://github.com/apache/tinkerpop/pull/483
TINKERPOP-1547: Two bugs found associated with MatchStep: Path retraction
and range count.
https://issues.apache.org/jira/browse/TINKERPOP-1547
Two bugs had always existed because we had commented out tests due to their
failure. Fixed the bugs and exposed more tests. Also, some `match()` benchmarks
got faster. Finally, I found a bug in `MatchStep.clone()` that only makes
itself apparent (and randomly) when there is a `match()`-step within a local
child of an OLAP traversal with single processor threading.
VOTE +1.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/tinkerpop TINKERPOP-1547
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tinkerpop/pull/483.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #483
----
commit e6266b12a0c90a7283231d2d435d1d677baccbfa
Author: Marko A. Rodriguez <[email protected]>
Date: 2016-11-08T17:02:37Z
fixed a bug in MatchStep that I forgot we had. Because of it, we had 3
tests commented out. Doh. The tests were a combination of problems in
PathRetractionsStrategy and RangeByIsCountStratyegy. Because of the fix in
PathRetractionStrategy, some match benchmarks got significantly faster.
commit 56e113da4878eb4e082b8589d323cbfa4efd31ac
Author: Marko A. Rodriguez <[email protected]>
Date: 2016-11-08T18:56:30Z
updated CHANGELOG and fixed a MatchStep.clone() bug that exposes itself in
OLAP traversals with OLTP match() children.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
