Sorry, I'm coming up empty in Google here.

---------------------------------------------------------------------

DirectoryReader.openIfChanged

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [EMAIL PROTECTED]
> -----Original Message-----
> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 05, 2012 4:54 PM
> To: [EMAIL PROTECTED]
> Subject: What replaces IndexReader.openIfChanged in Lucene 4.0?
>
> Sorry, I'm coming up empty in Google here.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------

The second item in the top section in trunk CHANGES.txt (back compat policy changes):
 
* LUCENE-2858, LUCENE-3733: IndexReader was refactored into abstract
  AtomicReader, CompositeReader, and DirectoryReader. To open Directory-
  based indexes use DirectoryReader.open(), the corresponding method in
  IndexReader is now deprecated for easier migration. Only DirectoryReader
  supports commits, versions, and reopening with openIfChanged(). Terms,
  postings, docvalues, and norms can from now on only be retrieved using
  AtomicReader; DirectoryReader and MultiReader extend CompositeReader,
  only offering stored fields and access to the sub-readers (which may be
  composite or atomic). SlowCompositeReaderWrapper (LUCENE-2597) can be
  used to emulate atomic readers on top of composites.
  Please review MIGRATE.txt for information how to migrate old code.
  (Uwe Schindler, Robert Muir, Mike McCandless)

-----Original Message-----
From: Benson Margulies [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 05, 2012 10:54 AM
To: [EMAIL PROTECTED]
Subject: What replaces IndexReader.openIfChanged in Lucene 4.0?

Sorry, I'm coming up empty in Google here.

---------------------------------------------------------------------

On Mon, Mar 5, 2012 at 11:07 AM, Steven A Rowe <[EMAIL PROTECTED]> wrote:
> The second item in the top section in trunk CHANGES.txt (back compat policy changes):

Could you guys put this on the web site (or a link to it)? Or try to
get it to SEO more prominently?

>
> * LUCENE-2858, LUCENE-3733: IndexReader was refactored into abstract
>  AtomicReader, CompositeReader, and DirectoryReader. To open Directory-
>  based indexes use DirectoryReader.open(), the corresponding method in
>  IndexReader is now deprecated for easier migration. Only DirectoryReader
>  supports commits, versions, and reopening with openIfChanged(). Terms,
>  postings, docvalues, and norms can from now on only be retrieved using
>  AtomicReader; DirectoryReader and MultiReader extend CompositeReader,
>  only offering stored fields and access to the sub-readers (which may be
>  composite or atomic). SlowCompositeReaderWrapper (LUCENE-2597) can be
>  used to emulate atomic readers on top of composites.
>  Please review MIGRATE.txt for information how to migrate old code.
>  (Uwe Schindler, Robert Muir, Mike McCandless)
>
> -----Original Message-----
> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 05, 2012 10:54 AM
> To: [EMAIL PROTECTED]
> Subject: What replaces IndexReader.openIfChanged in Lucene 4.0?
>
> Sorry, I'm coming up empty in Google here.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

---------------------------------------------------------------------

https://builds.apache.org//job/Lucene-trunk/lastSuccessfulBuild/artifact/artifacts/changes/Changes.html

-----Original Message-----
From: Benson Margulies [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 05, 2012 11:11 AM
To: [EMAIL PROTECTED]
Subject: Re: What replaces IndexReader.openIfChanged in Lucene 4.0?

On Mon, Mar 5, 2012 at 11:07 AM, Steven A Rowe <[EMAIL PROTECTED]> wrote:
> The second item in the top section in trunk CHANGES.txt (back compat policy changes):

Could you guys put this on the web site (or a link to it)? Or try to get it to SEO more prominently?

>
> * LUCENE-2858, LUCENE-3733: IndexReader was refactored into abstract
>  AtomicReader, CompositeReader, and DirectoryReader. To open
> Directory-
>  based indexes use DirectoryReader.open(), the corresponding method in
>  IndexReader is now deprecated for easier migration. Only
> DirectoryReader
>  supports commits, versions, and reopening with openIfChanged().
> Terms,
>  postings, docvalues, and norms can from now on only be retrieved
> using
>  AtomicReader; DirectoryReader and MultiReader extend CompositeReader,
>  only offering stored fields and access to the sub-readers (which may
> be
>  composite or atomic). SlowCompositeReaderWrapper (LUCENE-2597) can be
>  used to emulate atomic readers on top of composites.
>  Please review MIGRATE.txt for information how to migrate old code.
>  (Uwe Schindler, Robert Muir, Mike McCandless)
>
> -----Original Message-----
> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 05, 2012 10:54 AM
> To: [EMAIL PROTECTED]
> Subject: What replaces IndexReader.openIfChanged in Lucene 4.0?
>
> Sorry, I'm coming up empty in Google here.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

---------------------------------------------------------------------

To reduce noise slightly I'll stay on this thread.

I'm looking at this file, and not seeing a pointer to what to do about
QueryParser. Are jar file rearrangements supposed to be in that file?
I think that I don't have the right jar yet; all I'm seeing is the
'surround' package.

---------------------------------------------------------------------

You want the lucene-queryparser jar.  From trunk MIGRATE.txt:

* LUCENE-3283: Lucene's core o.a.l.queryParser QueryParsers have been consolidated into module/queryparser,
  where other QueryParsers from the codebase will also be placed.  The following classes were moved:
  - o.a.l.queryParser.CharStream -> o.a.l.queryparser.classic.CharStream
  - o.a.l.queryParser.FastCharStream -> o.a.l.queryparser.classic.FastCharStream
  - o.a.l.queryParser.MultiFieldQueryParser -> o.a.l.queryparser.classic.MultiFieldQueryParser
  - o.a.l.queryParser.ParseException -> o.a.l.queryparser.classic.ParseException
  - o.a.l.queryParser.QueryParser -> o.a.l.queryparser.classic.QueryParser
  - o.a.l.queryParser.QueryParserBase -> o.a.l.queryparser.classic.QueryParserBase
  - o.a.l.queryParser.QueryParserConstants -> o.a.l.queryparser.classic.QueryParserConstants
  - o.a.l.queryParser.QueryParserTokenManager -> o.a.l.queryparser.classic.QueryParserTokenManager
  - o.a.l.queryParser.QueryParserToken -> o.a.l.queryparser.classic.Token
  - o.a.l.queryParser.QueryParserTokenMgrError -> o.a.l.queryparser.classic.TokenMgrError
-----Original Message-----
From: Benson Margulies [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 05, 2012 11:15 AM
To: [EMAIL PROTECTED]
Subject: Re: What replaces IndexReader.openIfChanged in Lucene 4.0?

To reduce noise slightly I'll stay on this thread.

I'm looking at this file, and not seeing a pointer to what to do about QueryParser. Are jar file rearrangements supposed to be in that file?
I think that I don't have the right jar yet; all I'm seeing is the 'surround' package.

---------------------------------------------------------------------

OK, thanks.

On Mon, Mar 5, 2012 at 11:22 AM, Steven A Rowe <[EMAIL PROTECTED]> wrote:
> You want the lucene-queryparser jar.  From trunk MIGRATE.txt:
>
> * LUCENE-3283: Lucene's core o.a.l.queryParser QueryParsers have been consolidated into module/queryparser,
>  where other QueryParsers from the codebase will also be placed.  The following classes were moved:
>  - o.a.l.queryParser.CharStream -> o.a.l.queryparser.classic.CharStream
>  - o.a.l.queryParser.FastCharStream -> o.a.l.queryparser.classic.FastCharStream
>  - o.a.l.queryParser.MultiFieldQueryParser -> o.a.l.queryparser.classic.MultiFieldQueryParser
>  - o.a.l.queryParser.ParseException -> o.a.l.queryparser.classic.ParseException
>  - o.a.l.queryParser.QueryParser -> o.a.l.queryparser.classic.QueryParser
>  - o.a.l.queryParser.QueryParserBase -> o.a.l.queryparser.classic.QueryParserBase
>  - o.a.l.queryParser.QueryParserConstants -> o.a.l.queryparser.classic.QueryParserConstants
>  - o.a.l.queryParser.QueryParserTokenManager -> o.a.l.queryparser.classic.QueryParserTokenManager
>  - o.a.l.queryParser.QueryParserToken -> o.a.l.queryparser.classic.Token
>  - o.a.l.queryParser.QueryParserTokenMgrError -> o.a.l.queryparser.classic.TokenMgrError
>
>
> -----Original Message-----
> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 05, 2012 11:15 AM
> To: [EMAIL PROTECTED]
> Subject: Re: What replaces IndexReader.openIfChanged in Lucene 4.0?
>
> To reduce noise slightly I'll stay on this thread.
>
> I'm looking at this file, and not seeing a pointer to what to do about QueryParser. Are jar file rearrangements supposed to be in that file?
> I think that I don't have the right jar yet; all I'm seeing is the 'surround' package.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

---------------------------------------------------------------------