On a related note, schema updates are apparently not transactional at all. Is there any ability to run a db migration script with multiple schema changes in a way that will either complete entirely, or not at all? I'm concerned about our scripts failing halfway through and leaving the database in an unknown state.
Thanks On Thursday, 20 February 2014 23:04:29 UTC+13, Lvc@ wrote: > > Hi Jing, > I suggest you to migrate to 1.7-rc1 (or better 1.7-rc2) with better > management of cluster. However schema synchronization is supported in 1.6.x. > > Lvc@ > > > > On 7 January 2014 23:43, Jing Li <[email protected] <javascript:>> wrote: > >> Hi There, >> >> I currently have two instances running on the AWS within an OrientDB >> cluster (Replication turned on). Does the distributed mechanism support >> schema sync? What is the best practise to do a schema update in an OrientDB >> cluster? I am using 1.6.2 >> >> Thanks >> Jing >> >> -- >> >> --- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- --- 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/groups/opt_out.
