The bug getting edge attributes based on edge ids

[w158937299]

Version: 1.0.0

Storage Backend: inmemory

Mixed Index Backend: elasticresearch-8.6.0

API/Driver: Gremlin-python 3.2.6

Steps to Reproduce:

As shown in this figure, Query 1 returned the IDs of all edges in the graph data, and Query 2 had both graph database engines attempt to fetch corresponding attributes based on the edge IDs they queried, but both returned empty sets. Query 3 returned the attributes of all existing edges in the graph data, proving that edge attributes do exist. Query 4 was able to correctly retrieve results for corresponding attributes based on node IDs. We found it strange that Janusgraph were unable to execute operations to query corresponding attributes based on edge IDs.

[li-boxuan]

This does not look correct. JanusGraph edge IDs are strings like 557-388-9hx-3ag, not numbers.

[li-boxuan]

TinkerGraph, on the contrary, have numerical edge IDs. What you show here looks like JanusGraph edge ID.

[li-boxuan]

May I ask if this is a research project attempting to capture bugs of JanusGraph?

[w158937299]

Thank you for your reply, I'm sorry I wrote janusgraph and tinkergraph flags backwards. This is a research paper on detecting bugs in different graph databases.