Re: [Bigdata-developers] BTree key mismatch questions

[Fred O. <fko...@gm...>]

On Thu, Jul 15, 2010 at 4:29 PM, Bryan Thompson <br...@sy...> wrote:
> Fred,
>
>> 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.
>
> If you don't mind, can you apply and test the edit.  If you look in the configuration file (bigdataStandalone.config, bigdataCluster.config, bigdataCluster16.config), you will see the following line in each file.  It is part of the section where we are declaring the properties that will be applied to the triple store created by the batch job:
>
>        new NV(BigdataSail.Options.COLLATOR,"ASCII"),
>
> You should be able to just specify additional properties right there to override the locale, collator, etc.  The BigdataSail.Options is just inheriting options which include KeyBuilder.Options, so all of the options should be accessible in the BigdataSail.Options namespace.  You can also explictly reference them in the KeyBuilder.Options namespace if you feel that is clearer (but make sure to import that namespace at the top of the configuration file).

OK. That covers a few of the cases (maybe the important ones). But
there are DefaultKeyBuilderFactories created with empty or null
properties objects:

bigdata/src/java/com/bigdata/btree/DefaultTupleSerializer.java:
return new DefaultKeyBuilderFactory(new Properties());
bigdata/src/java/com/bigdata/btree/keys/KeyBuilder.java:        return
new DefaultKeyBuilderFactory(null/* properties */)
bigdata/src/java/com/bigdata/btree/NOPTupleSerializer.java:
new DefaultKeyBuilderFactory(new Properties()));
bigdata/src/java/com/bigdata/journal/Name2Addr.java:
new DefaultKeyBuilderFactory(new Properties())));

What are the consequences of unfortunate collators or locales in these places?

Fred