1

It looks like we can get Titan 1.0 use custom long ids by setting "graph.set-vertex-id" to true. Is there some way to use non-long (i.e. String) ids as Vertex Ids? Seeing that the Tinkerpop api supports Strings, and there's a feature called "StringIds", is there some way of enabling that feature? I'm using Titan with Cassandra.

ashic
  • 6,367
  • 5
  • 33
  • 54

2 Answers2

3

I think this goes against Titan's internal structure. One of the Titan devs recommends here to just use your own indexed property. This is reiterated here and here stating that unique indexed properties should be used.

I think the reason for this is that the internal ids actually refer to locations on the system. As stated here:

The (64 bit) vertex id (which Titan uniquely assigns to every vertex) is the key which points to the row containing the vertex’s adjacency list.

Community
  • 1
  • 1
Filipe Teixeira
  • 3,565
  • 1
  • 25
  • 45
  • hmm...that's surprising. Cassandra partition keys can be anything, and lookups would work just the same. And the Titan Apis, etc. (well Tinkerpop) suggests it should be possible. Then again, Titan uses the very old Thrift interface, and I'm thinking in CQL terms. – ashic Jul 06 '16 at 19:55
1

No, String identifiers are not supported in the StandardTitanGraph.features(). You could consider using an indexed String property as an alternative.

Jason Plurad
  • 6,682
  • 2
  • 18
  • 37