Phantom Unique Data / Data Too Large?
I've been chasing down a weird writing bug for our graph writer, but I feel like I've stumbled into conflicting realities in my graph and wanted to share in case I'm missing something larger. For context the environment in play is my local development environment, all running inside docker compose (host machine is MacOS, on the off chance it matters).
- JanusGraph 1.0.0
- Cassandra 4
- Elasticsearch 8
I'm writing vertices into a graph. I've got a property that is enforced uniqueness via a composite index with
The vertices also use custom vertex ids derived off this property. My thought was this way knowing the property I could go ahead and issue traversals against the vertex id instead of having to detour to an index, but still leverage the index when it was more convenient.
Trying to rerun some data for processing I'm having a violation of the aforementioned composite unique index, but I'm puzzled as to why.
Using gDotV I'm able to determine the following:
1. Querying based on the property that should use the unique index returns the vertex as expected with the expected custom id. However the properties off the vertex are empty like so when shown in gDotV:
2. Running just a query for the custom id as in
So this leaves me in a weird state that seems to be implying:
- The properties of the vertex are empty, but the unique index is still populated with the property, even when the vertex itself is not
- I'm not able to find the vertex with its vertex id
- JanusGraph 1.0.0
- Cassandra 4
- Elasticsearch 8
I'm writing vertices into a graph. I've got a property that is enforced uniqueness via a composite index with
unique()The vertices also use custom vertex ids derived off this property. My thought was this way knowing the property I could go ahead and issue traversals against the vertex id instead of having to detour to an index, but still leverage the index when it was more convenient.
Trying to rerun some data for processing I'm having a violation of the aforementioned composite unique index, but I'm puzzled as to why.
Using gDotV I'm able to determine the following:
1. Querying based on the property that should use the unique index returns the vertex as expected with the expected custom id. However the properties off the vertex are empty like so when shown in gDotV:
"properties": [],2. Running just a query for the custom id as in
g.V('id_goes_here')So this leaves me in a weird state that seems to be implying:
- The properties of the vertex are empty, but the unique index is still populated with the property, even when the vertex itself is not
- I'm not able to find the vertex with its vertex id
