Hi,
You did not answer my questions about the "id" poperty. TinkerPop uses a Token.ID that has the value 'id', see:

https://github.com/apache/tinkerpop/blob/master/gremlin-core/src/main/java/org/apache/tinkerpop/gremlin/structure/T.java

I suspect that you ingested data without schema validation ("automatic schema creation"), that your input data contains an "id¨ property key and that JanusGraph/TinkerPop get confused about which id is what. So I strongly suggest that you make sure that this is not the root cause of this issue. To be sure, it would still be an issue but not for you anymore :-)

Best wishes,    Marc

Another really strange observation

gremlin> g.V().has('id','131594d6a416666b401a9e48e54ebc8f22be75e2593c5d98e2d9ecfd719d5f29').has('type','email_sha256_lowercase').valueMap(true)
==>[dpts_678:[1595548800],label:vertex,id:201523209257056,id:[19df651e-90d5-47f6-af2e-35dcb59bcc0a],type:[id_mid_10],soft_del:[false],country_GBR:[678]]


Could you please have a look?

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 issue.

The issue is logged at https://github.com/JanusGraph/janusgraph/issues/2515

Thanks

Hi Saurabh,

The workaround you found has implications for performance. So, if you can describe how  to reproduce the issue, you can make an issue for it on https://github.com/JanusGraph/janusgraph/issues
This might easily be a scenario that is not covered by the current janusgraph tests.

I see that "id" is indeed a property key in the schema. I assume your input data already had this "id" property and this was not generated by janusgraph. In the former case does replacing "id" by "user_id" make any difference (this will make your queries more readable anyway)?

Best wishes,    Marc

Hi Marc

Hi Saurabh,

To be sure, in the valueMap(true) return value I see both the id token and an "id" property key appear (I am not even sure whether an "id" property key is allowed). Is this "id" property key something that was part of the input data of the graph? Can you also show the graph schema using:

mgmt = graph.openManagement()
mgmt.printSchema()

Best wishes,    Marc

We are facing a weird issue with Replication factor 3 with scylla DB as backend.  

- we are using index for looking up V in the graph
- observation is that for many vertices with the same index value, multiple vertex IDs are generated as seen below



Has anyone else encountered the same issue with RF3, with RF1 the issue is not encountered

Thanks
Saurabh Verma