You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@lucene.apache.org by Simon Willnauer <si...@googlemail.com> on 2011/08/22 18:24:00 UTC
heads up: re-index 3.x branch Lucene/Solr indices
I just reverted a previous commit related to CompoundFile in the 3.x
stable branch.
If you are using unreleased 3.x branch you need to reindex.
See here for details:
https://issues.apache.org/jira/browse/LUCENE-3218
If you are using a released version of Lucene/Solr then you can ignore
this message.
Thanks,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: heads up: re-index 3.x branch Lucene/Solr indices
Posted by Simon Willnauer <si...@googlemail.com>.
Shawn, as long as you are only using a release version of lucene /solr
you don't need to be worried at all. This is a index format change
that has never been released. only if you use a svn checkout you
should reindex.
simon
On Mon, Aug 22, 2011 at 8:56 PM, Shawn Heisey <so...@elyograg.org> wrote:
> On 8/22/2011 12:38 PM, Shawn Heisey wrote:
>>
>> Just to be clear, if you are not using a compound file, do you need to
>> worry about this? I am using 3.2, but I've got the compound file turned off
>> and have 11 files per segment. Upgrading is in my near future, but I think
>> 3.4 will be out by the time I get there.
>
> From what I've just been reading, Solr and Lucene default to using the
> compound file format. I started with 1.4.0, and now I'm not sure whether I
> turned it off or whether the example solrconfig.xml already had it turned
> off, but I know that it continues to be disabled because of performance
> worries. Do things still run faster if compound file format is off in the
> newest stable versions?
>
> Thanks,
> Shawn
>
>
Re: heads up: re-index 3.x branch Lucene/Solr indices
Posted by Shawn Heisey <so...@elyograg.org>.
On 8/22/2011 12:38 PM, Shawn Heisey wrote:
> Just to be clear, if you are not using a compound file, do you need to
> worry about this? I am using 3.2, but I've got the compound file
> turned off and have 11 files per segment. Upgrading is in my near
> future, but I think 3.4 will be out by the time I get there.
From what I've just been reading, Solr and Lucene default to using the
compound file format. I started with 1.4.0, and now I'm not sure
whether I turned it off or whether the example solrconfig.xml already
had it turned off, but I know that it continues to be disabled because
of performance worries. Do things still run faster if compound file
format is off in the newest stable versions?
Thanks,
Shawn
Re: heads up: re-index 3.x branch Lucene/Solr indices
Posted by Shawn Heisey <so...@elyograg.org>.
On 8/22/2011 10:24 AM, Simon Willnauer wrote:
> I just reverted a previous commit related to CompoundFile in the 3.x
> stable branch.
> If you are using unreleased 3.x branch you need to reindex.
>
> See here for details:
>
> https://issues.apache.org/jira/browse/LUCENE-3218
>
> If you are using a released version of Lucene/Solr then you can ignore
> this message.
Just to be clear, if you are not using a compound file, do you need to
worry about this? I am using 3.2, but I've got the compound file turned
off and have 11 files per segment. Upgrading is in my near future, but
I think 3.4 will be out by the time I get there.
Thanks,
Shawn