Another really strange observation gremlin>

Have you tried keeping query.batch = true AND query.fast-property = true? Regards, Boxuan

Hi All, Adding these properties in the configuration file affects edge traversal. Retrieving a single edge takes 7 mins of time. 1) Turn on query.batch 2) Turn off query.fast-property Count query is

Hi The issue still persists, and the vertex metadata is still missing for some vertices, after enabling https://docs.janusgraph.org/advanced-topics/eventual-consistency/, has someone seen the same

Opened the issue about this potential bug here: https://github.com/JanusGraph/janusgraph/issues/2524

Hi Fredrick, You are right, this is an issue, so if you want to report this: thanks. Best wishes, Marc

Hi Vinayak, Try below. If it works for you, you can add E2 and D similarly. g.V().has('property1', 'A'). outE().has('property1', 'E').as('e'). inV().has('property1', 'B').

Hi Boxuan Li, Hope this helps: --------------------------------------------------------------------------------------------------- Vertex Index Name | Type | Unique | Backing

Hi, can you share more details (what indexes do you have related to prop1 and/or prop2), or even minimal code to reproduce?

Hello We are on Janus 0.4.0 and faced one scenario wherein there were duplicate vertices created. These 2 vertices were created in span of 9 milliseconds within single transaction. We are using index

Thanks for your thoughts. 1) I'm very interested to try out the PR you made for this issue. 2) I don't think the solution you gave me in that previous thread solves the issue. What if another user

Amiya - I need to check the data, there is some mismatch with the counts. Consider we have more than one relation to get the count. How can we modify the query? For example: A->E->B query is as

Hi Vinayak, Correct vertex count is ( 400332 non-unique, 34693 unique). g.V().has('property1', 'A').aggregate('v'), all the vertex having property1 = A might be getting included in count in your

Hi Amiya, With dedup: g.V().has('property1', 'A'). outE().has('property1','E'). where(inV().has('property1', 'B')). fold(). project('edgeCount', 'vertexCount').

Hi Vinayak, May be try below. g.V().has('property1', 'A'). outE().has('property1','E'). where(inV().has('property1', 'B')). fold(). project('edgeCount', 'vertexCount').

Hi Claire! Would you mind sharing the pom.xml file for your build? I'm trying a similar build for AWS and am hitting a mess of dependency errors. Thank you :) Ben

Hi Srinivas, In the yaml file determining class Settings you use the channelizer key twice. If you use ConfigurationManagentGraph only the following line should be present: channelizer:

Hi Vinayak, Another attempt, this one is very similar to the one that works. gremlin> graph =

Hi, You may try to use denormalization by setting property1 from inV also on edge. Then once edges are updated, following query should work: g.V().has('property1',

Hi Marc, Using local returns the output after each count. For