|
From: Fred O. <fko...@gm...> - 2010-07-15 20:17:57
|
On Thu, Jul 15, 2010 at 12:47 PM, Bryan Thompson <br...@sy...> wrote: > Fred, > > I think that the local of the machine should control the default since it is > more likely to be correct and more transparent with the OS/Java stack. You > can specify this in the bigdataCluster.config file for scale-out or the > Properties for a Journal. I am happy to specify en_US in the sample > configuration files. That makes it pretty obvious where people can override > this behavior. Yes, please add that locale to the sample configuration files. I think it should be made reasonably obvious that the locale of the machine and the locale of the data need not be related. Otherwise, if different machines (containing different shards or clients) in a single cluster had different locale settings, then would all the machines be creating or processing keys in a single BTree with the same locale? >> The choice of language appears to be left to default system properties >> which can also vary from VM to VM. > > The choice is made based on the local environment, but it is captured by the > IndexMetadata object and imposed on any machine which uses that index. If BTree indices are split and shards moved to machines with different locale settings, then will the IndexMetadata object on both machines necessarily agree? What is the origin of the (content of the) IndexMetadata object? Fred |