If order is critical, it is difficult to rely on time in a distributed setup because there are often at least slight variations in time between nodes that could cause items to be out-of-sequence. And assuming time was in perfect sync, there are still the same issues with identical timestamps from active systems. Everything has a trade-off, and in this case it's great to see I can still force everything to a single cluster. I also filed a bug report regarding the SQL keyword CLUSTER not working properly.
-- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
