Hi guys:

   In the codec api, it seems you can set term order via an arbitrary
Comparator<BytesRef>.

   I tried to use this to create a term dictionary of an order dictated by
my own Comparator<BytesRef>.

   The problem arises when building the FST. Specifically
BlockTreeTermsWriter.finishTerm() <- here the ordering decided earlier by
the Comparator<BytesRef> (from codec) is lost, and errors due to out of
order.

   Any ideas on how to fix this?

Thanks

-John

Reply via email to