You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We discovered a bug that Throw ExecutionException for E() syntax.
OrientDB version: 3.2.14
Operating system: macOS 13.2.1
API/Driver: Java
I first randomly create a graph. Then when I run the following query: g.E().inV().inE('el1','el3').as('a').E().not(__.values('ep8')).as('b').select('a').where('a',eq('b')) is thrown with an exception. I think this query is syntactically correct, but I keep triggering this kind of problem. I generate the query based on the rule which can be refered from: https://stackoverflow.com/questions/48067834/gremlin-intersection-operation. Following this instruction, I think it's allowed to generate this kind of queries.
Expected behavior:
No exception should be expected to throw. Or futher messages or prompts should be thrown.
Actual behavior:
A java.util.concurrent.ExecutionException is thrown. And I'm not really sure whether this problem should happen so I report this. I succeed this kind of collection transition when replacing g.E() with g.V(). So I guess there's some problems of g.E() syntax. I report just in case
Orientdb exception :
java.util.concurrent.ExecutionException: org.apache.tinkerpop.gremlin.driver.exception.ResponseException: No signature of method: org.apache.tinkerpop.gremlin.process.traversal.dsl.graph.DefaultGraphTraversal.E() is applicable for argument types: () values: []
Possible solutions: by(groovy.lang.Closure), is(java.lang.Object), use([Ljava.lang.Object;), use(java.util.List, groovy.lang.Closure), use(java.lang.Class, groovy.lang.Closure), any()
Steps to reproduce:
We create a graph with 10 nodes and 20 edges. We try to make it clear to reproduce the bugs, hope to not cause much inconvenience to your reviewing, but we believe the problem does exist.
Following the following graph data generation query, we can reproduce the bugs:
This may be caused by the fact that orientdb 3.2.14 had a bit outdate gremling version, could you check with orientdb 3.2.18 or newer, we did update gremlin libraries in that version.
We discovered a bug that Throw ExecutionException for E() syntax.
I first randomly create a graph. Then when I run the following query:
g.E().inV().inE('el1','el3').as('a').E().not(__.values('ep8')).as('b').select('a').where('a',eq('b'))
is thrown with an exception. I think this query is syntactically correct, but I keep triggering this kind of problem. I generate the query based on the rule which can be refered from: https://stackoverflow.com/questions/48067834/gremlin-intersection-operation. Following this instruction, I think it's allowed to generate this kind of queries.Expected behavior:
No exception should be expected to throw. Or futher messages or prompts should be thrown.
Actual behavior:
A
java.util.concurrent.ExecutionException
is thrown. And I'm not really sure whether this problem should happen so I report this. I succeed this kind of collection transition when replacingg.E()
withg.V()
. So I guess there's some problems ofg.E()
syntax. I report just in caseSteps to reproduce:
We create a graph with 10 nodes and 20 edges. We try to make it clear to reproduce the bugs, hope to not cause much inconvenience to your reviewing, but we believe the problem does exist.
Following the following graph data generation query, we can reproduce the bugs:
The text was updated successfully, but these errors were encountered: