[
https://issues.apache.org/jira/browse/TINKERPOP-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855781#comment-16855781
]
ASF GitHub Bot commented on TINKERPOP-2230:
-------------------------------------------
dkuppitz commented on pull request #1124: TINKERPOP-2230 Fixed bug in match()
step
URL: https://github.com/apache/tinkerpop/pull/1124
https://issues.apache.org/jira/browse/TINKERPOP-2230
Fixed a bug where `MatchStep()` didn't determine the correct start step
properly.
**Before**
```
gremlin> g.V().match(
......1> __.as('a').out('knows').as('b'),
......2> __.as('b').out('created').as('c'))
==>[a:v[1],b:v[4],c:v[5]]
==>[a:v[1],b:v[4],c:v[3]]
gremlin> g.V().match(
......1> __.as('b').out('created').as('c'),
......2> __.as('a').out('knows').as('b'))
The provided match pattern is unsolvable: [[MatchStartStep(a),
VertexStep(OUT,[knows],vertex), MatchEndStep(b)], [MatchStartStep(b),
VertexStep(OUT,[created],vertex), MatchEndStep(c)]]
```
**Now**
```
gremlin> g.V().match(
......1> __.as('a').out('knows').as('b'),
......2> __.as('b').out('created').as('c'))
==>[a:v[1],b:v[4],c:v[5]]
==>[a:v[1],b:v[4],c:v[3]]
gremlin> g.V().match(
......1> __.as('b').out('created').as('c'),
......2> __.as('a').out('knows').as('b'))
==>[a:v[1],b:v[4],c:v[5]]
==>[a:v[1],b:v[4],c:v[3]]
```
`docker/build.sh -t -i` passed.
VOTE +1
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> match() step unexpected behaviours
> ----------------------------------
>
> Key: TINKERPOP-2230
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2230
> Project: TinkerPop
> Issue Type: Bug
> Components: process
> Affects Versions: 3.4.1
> Reporter: Fabio Lorenzi
> Assignee: Daniel Kuppitz
> Priority: Major
> Labels: gremlin
>
> On the well known software graph:
> {code:java}
> gremlin> g.V().match(
> ......1> __.as('a').out('knows').as('b'),
> ......2> __.as('b').out('created').as('c'))
> ==>[a:v[1],b:v[4],c:v[5]]
> ==>[a:v[1],b:v[4],c:v[3]]
> gremlin> g.V().match(
> ......1> __.as('b').out('created').as('c'),
> ......2> __.as('a').out('knows').as('b'))
> The provided match pattern is unsolvable: [[MatchStartStep(a),
> VertexStep(OUT,[knows],vertex), MatchEndStep(b)], [MatchStartStep(b),
> VertexStep(OUT,[created],vertex), MatchEndStep(c)]]
> {code}
> with the second one being solvable as well (I think). (?)
> Quoting [~dkuppitz]:
> "I just noticed that the error message of my failing traversal actually
> contains a solvable form of patterns. It's really confusing; if you want,
> create a Jira ticket for that issue, perhaps someone dares to analyze that
> crazy code"
> please see
> [this|https://stackoverflow.com/questions/56218188/match-clause-is-unsolvable-behavior-is-not-clear/56260508#56260508]
> for more information.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
