Muthu, Yes, you can use IgniteUUID as unique ID generator. What you will use depends your requirements. IgniteAtomicSequence takes one long and IgniteUUID takes 3 long. But getting new range sequence is distributed operation. You need to decied what more critical for your.
On Fri, Jun 9, 2017 at 8:46 PM, Muthu <[email protected]> wrote: > > Missed adding this one...i know there is support for ID generation with > IgniteAtomicSequence @ https://apacheignite.readme.io/docs/id-generator > > The question is which one should i use...i want to use this to generate > unique ids for entities that are to be cached & persisted.. > > Regards, > Muthu > > > On Fri, Jun 9, 2017 at 10:27 AM, Muthu <[email protected]> wrote: > >> Hi Folks, >> >> Is it possible to generate a Grid/Cluster unique UUID using IgniteUuid. I >> looked at the source code & static factory method *randomUuid >> <https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/lang/IgniteUuid.html#randomUuid%28%29>*(). >> It looks like it generates one with with a java.util.UUID (generated with >> its randomUUID) & an AutomicLong's incrementAndGet >> >> Can i safely assume that given that it uses a combination of UUID & long >> on the individual VMs that are part of the Grid/Cluster it will be unique >> or is there a better way? >> >> Regards, >> Muthu >> > >
