Problem with Custom Long IDs in JanusGraph
Hi,
I'm experiencing issues with using custom Long IDs in JanusGraph. Although I'm aware of the limitations concerning signed long integers, I'm still facing problems with the range of IDs that can be utilized. Currently, I'm operating with two Cassandra machines as backend storage and a single JanusGraph machine.
My database needs to handle at least 3 billion vertex nodes with unique IDs, and I'm trying to determine if this is feasible. I've experimented with various configuration settings, such as cluster.max-partitions and ids.authority.conflict-avoidance-bitwidth, attempting to expand the number of bits available for IDs, but without success.
I'm starting to suspect that the issue might be related to my Cassandra configuration. Could you provide insights into how the Cassandra settings should be adjusted to support a larger ID range? Specifically, are there any configurations related to partitioning, replication, or data types that I need to modify to accommodate a higher number of unique IDs?
Additionally, if it's not possible to use Long IDs in this circumstance, are there any downsides to using String IDs instead? If so, do you have any recommendations on how to effectively manage random IDs in this scenario?
Any guidance on this matter would be greatly appreciated.
I'm experiencing issues with using custom Long IDs in JanusGraph. Although I'm aware of the limitations concerning signed long integers, I'm still facing problems with the range of IDs that can be utilized. Currently, I'm operating with two Cassandra machines as backend storage and a single JanusGraph machine.
My database needs to handle at least 3 billion vertex nodes with unique IDs, and I'm trying to determine if this is feasible. I've experimented with various configuration settings, such as cluster.max-partitions and ids.authority.conflict-avoidance-bitwidth, attempting to expand the number of bits available for IDs, but without success.
I'm starting to suspect that the issue might be related to my Cassandra configuration. Could you provide insights into how the Cassandra settings should be adjusted to support a larger ID range? Specifically, are there any configurations related to partitioning, replication, or data types that I need to modify to accommodate a higher number of unique IDs?
Additionally, if it's not possible to use Long IDs in this circumstance, are there any downsides to using String IDs instead? If so, do you have any recommendations on how to effectively manage random IDs in this scenario?
Any guidance on this matter would be greatly appreciated.
