Not sure if plain users are allowed/encouraged to post in this list, but wanted to mention (just an opinion from a happy user), as other users have, that not all of us can reindex just like that. It would not be 10 min for one of our installations for sure...
First, i would need to implement some code to reindex, cause my source data is postprocessed/compressed/encrypted/moved after it arrives to the application, so I would need to retrieve all etc. And then reindexing it would take days. javier On Thu, Apr 15, 2010 at 9:04 PM, Earwin Burrfoot <ear...@gmail.com> wrote: >> BTW Earwin, we can come up w/ a migrate() method on IW to accomplish >> manual migration on the segments that are still on old versions. >> That's not the point about whether optimize() is good or not. It is >> the difference between telling the customer to run a 5-day migration >> process, or a couple of hours. At the end of the day, the same >> migration code will need to be written whether for the manual or >> automatic case. And probably by the same developer which changed the >> index format. It's the difference of when does it happen. > > Converting stuff is easier then emulating, that's exactly why I want a > separate tool. > There's no need to support cross-version merging, nor to emulate old APIs. > > I also don't understand why offline migration is going to take days > instead of hours for online migration?? > WTF, it's gonna be even faster, as it doesn't have to merge things. > > -- > Kirill Zakharenko/Кирилл Захаренко (ear...@gmail.com) > Home / Mobile: +7 (495) 683-567-4 / +7 (903) 5-888-423 > ICQ: 104465785 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
