Maybe raise an issue on this?
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn http://www.linkedin.com/in/neubauer
Twitter http://twitter.com/peterneubauer
http://www.neo4j.org - NOSQL for the Enterprise.
When guaranteed uniqueness on index-level is supported this can probably be
implemented. Have one indirection in an index adds overhead but I image
it's only for one or more starting points and then it's internal ids all
the way from there.
2011/11/9 Michael Hunger
Hi,
is there any news on implementing native UUID in Neo4j?
Back in May 2010, there was a discussion about UUID in Neo:
http://lists.neo4j.org/pipermail/user/2010-May/003625.html
Greetings
Axel
___
Neo4j mailing list
User@lists.neo4j.org
Well,
per se it is probably not going to happen soon, but as Jim etc are
starting on the sharding work, there might be a chance to put a layer
of indirection in to resolve IDs to shards.
Any thoughts on that Jim?
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Hey Peter,
I think you raise a good point. We'll need some kind of ID for objects stored
in (v)shards, but that's likely to be some kind of hierarchical ID (so that we
can locally and globally refer to objects in and across shards).
I think here the question boils down to: can we add (fast)
I think a separate UUID (2xLONG = 16 Bytes) property type would make sense, if
I remember correctly property types with larger block sizes are now possible.
Otherwise it could be an inlined long[2].
Having good support on the API level (integrated separate fast index +
uniqueness) would be
6 matches
Mail list logo