If you cluster your users based on country/location, can you later move them from one cluster to another (if they change their location)?

[jonmdev]

I am looking at the documentation and it states:

A class can rely on multiple clusters. You can spawn records physically in multiple places, thereby creating multiple clusters. For example:
The class "Customer" relies on 2 clusters:
USA_customers, containing all USA customers. This is the default cluster as denoted by the red star.
China_customers, containing all Chinese customers.
If you know the location of a customer you're looking for you can query the target cluster directly. This avoids scanning the other clusters and optimizes the query:

https://orientdb.org/docs/2.0/orientdb.wiki/Tutorial-Clusters.html

If one is developing a location based social database like for a dating or meetup app, this optimization would be very important. 99% of queries will be only within one country/continent/region rather than crossing regional borders.

However, if a user then moves from one location to another, is there any easy way to move them in the database? Ie. In the example above, could we move "BobSmith2458" from "USA_customers" to "China_customers" if we become aware he has now moved to China?

If "BobSmith2458" has a bunch of edges and other connections associated with him, can we move him without breaking those connections?

Would we have to copy and clone all the data and then delete the original, or could a true "move" be done? How would you handle such a user move?

Thanks for any thoughts or ideas.

[jonmdev]

Looks like this is here as far as I can tell:

https://orientdb.org/docs/3.0.x/sql/SQL-Move-Vertex.html