Re: svn commit: r928246 [1/6] - in /lucene/java/branches/flex_1458: ./ backwards/src/ backwards/src/java/org/apache/lucene/search/ backwards/src/test/org/apache/lucene/analysis/ backwards/src/test/o

2010-03-27 Thread Michael McCandless
Right. But now that public copyTo takes list-of-files I think "expert" apps can do the right thing here. Worst case is they .listAll but then filter out the files they know they add to index dir. Mike On Sat, Mar 27, 2010 at 4:56 PM, Earwin Burrfoot wrote: > Well, it was a back-compat break fr

Re: svn commit: r928246 [1/6] - in /lucene/java/branches/flex_1458: ./ backwards/src/ backwards/src/java/org/apache/lucene/search/ backwards/src/test/org/apache/lucene/analysis/ backwards/src/test/o

2010-03-27 Thread Michael McCandless
Ugh, actually, it is still a back-compat break :( Because Directory.copy just forwards to copyTo. I'll advertise in CHANGES for flex. Mike On Sat, Mar 27, 2010 at 4:41 PM, Michael McCandless wrote: > Right... in fact as long as we land flex before 3.1 releases then this > is not a back-compat

Re: svn commit: r928246 [1/6] - in /lucene/java/branches/flex_1458: ./ backwards/src/ backwards/src/java/org/apache/lucene/search/ backwards/src/test/org/apache/lucene/analysis/ backwards/src/test/o

2010-03-27 Thread Michael McCandless
Right... in fact as long as we land flex before 3.1 releases then this is not a back-compat break (but we should heavily advertise the change in semantics) ;) Ie Directory.copy used to filter for only index files, but Directory.copyTo copies everything so you must provide your own list if this mat

Re: svn commit: r928246 [1/6] - in /lucene/java/branches/flex_1458: ./ backwards/src/ backwards/src/java/org/apache/lucene/search/ backwards/src/test/org/apache/lucene/analysis/ backwards/src/test/o

2010-03-27 Thread Michael McCandless
I'm merging the conflicts now... it turned out to cause a number of conflicts because in flex I changed how DW stores the terms in RAM, to first prefix-code each term's length as vInt (most often 1 byte, but in messed up cases 2 bytes), and then then the term's characters as UTF8 bytes. This cause