If you write all INSERTs from a single node, yes, but because sharding is
where each node has its own cluster within a Class, that wouldn't be the
case if you INSERT on different nodes:
ie. INSERT on Node1: adds MyClass_Node1, @rid = #17:236
INSERT on Node2: adds MyClass_Node2, @rid = #18:54
INSERT on Node3: adds MyClass_Node3, @rid = #19:7632
so they are all MyClass, but different clusters, with a different high @rid
which you can't use for sorting over the entire class.
One possible workaround might be simply to always try writing to the
default cluster for a class directly, but I think there may be limitations
on that right now.
On Monday, June 8, 2015 at 3:52:51 AM UTC-4, scott molinari wrote:
>
> Isn't that what OrientDB does?
>
> http://orientdb.com/docs/last/Distributed-Sharding.html
>
> Scott
>
--
---
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.
