Hi all! From Discord.
We noticed that in some cases unsolvable matching will not lead to the exception "unsolvable pattern" in Gremlin.
For a simple example, in the empty graph, the following query will not lead to an exception, while it will result in an exception in the GraphModern:
In more complex cases, this missing may lead to a worse result.
For example, in the graph created by attachment create-8.log
The two queries are equivalent, the only difference is the expression of the traversal "__.as("n4").both().out().out().out().out().as("n2")".
I am not sure which of their results in the correct result, but the logic inconsistency indicates that the missing exception may cause worse results than we thought before.
After the discussion with spmallette, we believe that it would be better if detect the unsolvable pattern before the execution.
In addition, it would be highly appreciated if someone can reproduce and confirm the logic inconsistency in the complex cases. I think it may imply other potential issues of the traversal strategies. And if such logic inconsistency still exists using both solvable equivalent patterns, we will reduce & report is ASAP.