On Mon, Jun 13, 2011 at 8:14 PM, Chris Hostetter
wrote:
>
> : Since nobody objected to the idea, I created the following templates
> : for 3.3, and added a few already-committed things.
>
> I like the idea ... but why not just keep in in SVN?
>
> (that way patches can suggest wording for hte relea
: Since nobody objected to the idea, I created the following templates
: for 3.3, and added a few already-committed things.
I like the idea ... but why not just keep in in SVN?
(that way patches can suggest wording for hte release notes if/when the
patch is contains a notable feature worthy of
Since nobody objected to the idea, I created the following templates
for 3.3, and added a few already-committed things.
http://wiki.apache.org/lucene-java/ReleaseNote33
http://wiki.apache.org/solr/ReleaseNote33
If we can try to keep this up to date, besides saving the release
manager some time, i
: Ryan McKinley [mailto:ryan...@gmail.com]
> Sent: Friday, June 03, 2011 9:14 PM
> To: dev@lucene.apache.org
> Subject: Re: Upgrading from Solr 1.2 to 3.1/2 (was: Re: tentative! release
> notes drafts)
>
> When upgrading Solr from 1.x to 3.x it is *highly* recommended to re-index
>
hanged. In case it matters, i'm using
> EnglishPorterFilterFactory.
>
>
> -JM
>
> -Original Message-
> From: Uwe Schindler
> To: dev@lucene.apache.org
> Sent: Fri, Jun 3, 2011 12:04 pm
> Subject: RE: tentative! release notes drafts
>
> You must only reindex, if y
shPorterFilterFactory.
-JM
-Original Message-
From: Uwe Schindler
To: dev@lucene.apache.org
Sent: Fri, Jun 3, 2011 12:04 pm
Subject: RE: tentative! release notes drafts
You must only reindex, if you *change* the Analyzers to different ones. If you
keep the old schemas and ensure that tokeniz
e/> http://www.thetaphi.de
eMail: u...@thetaphi.de
From: johnmu...@aol.com [mailto:johnmu...@aol.com]
Sent: Friday, June 03, 2011 5:01 PM
To: dev@lucene.apache.org
Subject: Re: tentative! release notes drafts
So, in my case, upgrading from Solr 1.2 to 3.2, I must re-index. OK, I got
that, than
.apache.org/viewvc/lucene/dev/trunk/lucene/src/java/org/apache/lucene/index/IndexUpgrader.java?view=markup
simon
>
> -JM
>
> -Original Message-
> From: Uwe Schindler
> To: dev@lucene.apache.org
> Sent: Fri, Jun 3, 2011 10:52 am
> Subject: RE: tentative! release notes
2011 10:52 am
Subject: RE: tentative! release notes drafts
Hi,
When analyzers change behavior you have to reindex, there is no way around. The
index-upgrader tool simply rewrites index segments to the new file format, but
does not change contents.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 6
; http://www.thetaphi.de
eMail: u...@thetaphi.de
From: johnmu...@aol.com [mailto:johnmu...@aol.com]
Sent: Friday, June 03, 2011 4:47 PM
To: dev@lucene.apache.org
Subject: Re: tentative! release notes drafts
Hi,
Looking at http://wiki.apache.org/lucene-java/ReleaseNote32, the item:
*
011 7:02 pm
Subject: tentative! release notes drafts
Hello,
While we await the results of the vote (72 hours), I thought it would
e good to propose something new for the release emails, by putting
omething up on the wiki where anyone can just edit it. In the past,
e would email each other bac
Hello,
While we await the results of the vote (72 hours), I thought it would
be good to propose something new for the release emails, by putting
something up on the wiki where anyone can just edit it. In the past,
we would email each other back and forth and I think that's not the
easiest way to b
12 matches
Mail list logo
