Re: [Bigdata-developers] BTree key mismatch questions

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

On Thu, Jul 15, 2010 at 12:47 PM, Bryan Thompson <br...@sy...> wrote:
> Fred,
>
>> The bug was detected when the icu4j jar was inadvertently left out of a
>> classpath in a test environment. The decision to choose a default key
>> encoding based on whether a class can be loaded is undesirable because two
>> different virtual machines can attempt to use different key encodings on the
>> same BTree. Would you object to always using ICU as the default for now (and
>> possibly using an explicit configuration option in the future)?
>
> I would be fine making ICU the default.  You can explicitly configure this
> using KeyBuilder.Options.COLLATOR and specifying "ICU" as the value for that
> option.  (I will note in passing that the ICU4JNI option has not been tested
> but might offer some performance benefits if it could be made to work.
> Also, I have not checked the current release of ICU -- we might be able to
> update our dependency.)

I've made ICU the default as of svn #3203. By configure, I meant
changing a configuration file at deployment time.

Fred