On Mon, May 3, 2010 at 9:07 AM, Uwe Schindler <[email protected]> wrote:
> In current flex, the TermsEnum has a method called getComparator() that > returns the comparator used in this TermsEnum. This is the reason behind it. > If we change this to only support natural byte[] ordering (of course > unsigned, die, die Java's signedness of byte!), and codecs should not > support other ordering in future (In my opinion this would break most MTQs > depending on the order like range, fuzzy, wildcard,*), its obsolete. > Yeah even simpler ones like PrefixQuery will break if you were to change the sort order to say, sort backwards... so I think this is a very expert customization. -- Robert Muir [email protected]
