lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Muir <rcm...@gmail.com>
Subject Re: Build failed in Hudson: Lucene-trunk #1187
Date Fri, 14 May 2010 15:16:04 GMT
On Fri, May 14, 2010 at 10:59 AM, Yonik Seeley
<yonik@lucidimagination.com> wrote:

> So it seems like the biggest issue we might have in cutting over would
> be the field cache and sorting?  Instead of using String.compareTo we
> need one that compares as UTF-32 (or longer term, don't even create
> strings of course...)

Admittedly not having looked at all the places that do
String.compareTo on terms [I am sure there are probably more?], I
wonder if its worth the effort up front to just go completely to bytes
for Term and everything.

I worry about using a special String comparator: any code, including
stuff thats not in Lucene/Solr, that puts these things into ordered
collections for example could have bugs.

If we instead move all of this to BytesRef where the comparator just
works by default, it seems less scary.

-- 
Robert Muir
rcmuir@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message