redtree1112
ATApache TinkerPop
•Created by dbns97 on 8/31/2023 in #questions
PropertiesStep.hashcode() not always unique
On the other hand, @dbns97_61020 's issue is that we have the exact same
PropertiesStep under the same traversal.
I am not sure if we need to improve that part, a user might need to specify the Step they want by its index, or use == and compare by reference (you need the reference of the exact object in advance though). You may also rely on Step ID to identify some Step in such case as well.5 replies
ATApache TinkerPop
•Created by dbns97 on 8/31/2023 in #questions
PropertiesStep.hashcode() not always unique
It is a bit different issue, the JIRA ticket is about having redundant parameters will have a conflict because it relies on
XOR to compute hashCode. I am working on a fix.5 replies
ATApache TinkerPop
•Created by bulletlegend on 8/1/2023 in #questions
Gremlin query has strange behavior with range() and limit()
Hmm let me see.
Unfortunately
Neptune#chunkSize is publicly available but we did not publish the information because this query hint generally does no good and it is intended only for debugging.
Can you run profile while adding chunkSize ? I want to see if the chunkSize is actually changed in the plan.17 replies
ATApache TinkerPop
•Created by Lyndon on 8/23/2023 in #questions
Casting issue with Gremlin Java
Ah I see. Does specifying a type in generics above work ?
9 replies
ATApache TinkerPop
•Created by Lyndon on 8/23/2023 in #questions
Casting issue with Gremlin Java
or does this work ?
9 replies
ATApache TinkerPop
•Created by Lyndon on 8/23/2023 in #questions
Casting issue with Gremlin Java
I may be missing something but if you
unfold() immediately after fold(), can you just omit it ?9 replies
ATApache TinkerPop
•Created by Jim Idle on 8/17/2023 in #questions
AWS Neptune bulk load notifications
Let me check. I will ask internally in Neptune team. I am not an expert on bulk load.
7 replies
ATApache TinkerPop
•Created by bulletlegend on 8/1/2023 in #questions
Gremlin query has strange behavior with range() and limit()
1000 may not be enough if a number of items returned is big. So you may need to set large enough number to test all solutions under
not. I know this is not ideal, Neptune needs a better solution in a long term.17 replies
ATApache TinkerPop
•Created by bulletlegend on 8/1/2023 in #questions
Gremlin query has strange behavior with range() and limit()
As a workaround, can you try the query hint
g.withSideEffect("Neptune#chunkSize", 1000) and see if the issue is resolved ?
1000 is the default chunkSize in Neptune, so it won't harm more than the normal behavior.17 replies
ATApache TinkerPop
•Created by bulletlegend on 8/1/2023 in #questions
Gremlin query has strange behavior with range() and limit()
Yeah this is indeed caused by chunkSize optimization in Neptune. However the fix wouldn't be straightforward, let me talk internally in Neptune team.
17 replies
ATApache TinkerPop
•Created by bulletlegend on 8/1/2023 in #questions
Gremlin query has strange behavior with range() and limit()
Thanks for reporting. This can be reproduced with Modern graph with this simple query:
g.V('3').local(not(__.in("created").hasId('6')).limit(1)).limit(1)
I believe the chunk size that Neptune uses for optimization does something wrong. I am investigating the issue.17 replies