-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable .is(neq(' cypher.null'))
Gremlin token for Cyphter statements that contains WITH
clause
#342
Comments
such option will also make possible to avoid parameters in-lining which mentioned here |
@dwitry could you please share your thoughts on this? |
Any updates on this? Please, advise! |
Hey @dwitry, have you had a chance to have a look at this yet? :) |
@sbespalov @steve-todorov This change requires either implementing optimization strategy or introduce an inlining option. Both of these changes require significant efforts in development and testing. Currently, all my attention is focused on other areas, and I can not provide any terms when this could be implemented. The best I can do is review and merge PR if there are any volunteers. |
@dwitry , Thanks for your reply! Would it be possible to outline the list of tasks that you think would be required in order to implement/fix this? |
有人怎么解决的吗?求分享下了。 |
I have following Cyphter statement:
This statement produce following Gremlin query:
There is also index on
uuid
property forRepositoryArtifactIdGroup
vertex in JanusGraph, so I expect this query should trigger this index.The problem is that for some reason index not triggered directly this way, but it works fine without
.is(neq(' cypher.null'))
token. I am not sure does it JanusGrapth issue or not but however it will be good to optionally disable thiscypher.null
to be generated.Is it possible to have such option?
The text was updated successfully, but these errors were encountered: