The IndexWriter diagnostics (LUCENE-1654: recording Lucene version,
Java/OS version, etc into each segment created) also bumped the index
file format.

And LUCENE-1623 (fixing back-compat issue w/ field names that have
non-ascii characters) also bumped the format of the fnm file.

Offhand I can't think of other issues that might change the format...
but we do have a lot of open 2.9 issues so I guess it's possible.

Does Solr use NIOFSDirectory/MMAPDirectory by default?

> We're passing docsScoredInOrder=true

Excellent!  I'm wanting Lucene to do the same, in IndexSearcher when
we create the collector, for most queries.

And

On Wed, May 27, 2009 at 6:23 PM, Yonik Seeley
<yo...@lucidimagination.com> wrote:
> We're aiming for a Solr release in the next few weeks (as usual, we're
> 6 months behind when we wanted to make the release).
> The catch is that Solr depends on Lucene 2.9, and there have been a
> *lot* of changes.  We're currently on r779312 (upgraded topday).
>
> I'll add a note to Solr to warn users from using new Lucene APIs in
> plugins, and warn them to not upgrade the version of Lucene in Solr
> themselves.  Solr itself doesn't require API back compat from Lucene
> of course... we'll figure out some way to get stuff to work.
>
> So concerns what does that leave?
> - Index format stability... I believe since 2.4, the only change has
> been commit metadata?  Any guesses if the format for this remain
> stable until 2.9 is released?
> - stability in general (i.e. not crashing or producing corrupt indexes)
>
> Solr is using read-only readers, IndexReader.reopen(),
> IndexReader.incRef(), etc.  All deletes are via IndexWriter
> We're also using the new Collector classes, new FieldComparator
> classes including custom comparators.  We're passing
> docsScoredInOrder=true, and we also depend on docs coming back in
> sorted order in some places.
>
> Solr is *not* using NRT features.
>
> Any thoughts or concerns?  Any specific changes we should wait for?
>
> -Yonik
> http://www.lucidimagination.com
>
> ---------------------------------------------------------------------
> 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

Reply via email to