See:
https://issues.apache.org/jira/browse/SOLR-330
https://issues.apache.org/jira/browse/SOLR-342
for various solutions around taking advantage of Lucene's new
capabilities.
-Grant
On Feb 12, 2008, at 1:15 PM, Yonik Seeley wrote:
On Feb 12, 2008 1:06 PM, Lance Norskog <[EMAIL PROTECTED]
On Feb 12, 2008 1:06 PM, Lance Norskog <[EMAIL PROTECTED]> wrote:
> What will this improve?
Text analysis may be slower since Solr won't have the changes to use
the faster Token APIs.
Indexing overall should still be faster.
Querying should see little change.
-Yonik
What will this improve?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yonik Seeley
Sent: Tuesday, February 12, 2008 6:48 AM
To: solr-user@lucene.apache.org
Subject: Re: upgrading to lucene 2.3
On Feb 12, 2008 9:25 AM, Robert Young <[EMAIL PROTEC
I did the same:
Stopped SOLR-1.2, replaced Lucene jars, started SOLR-1.2
No any problem.
> -Original Message-
> From: Robert Young [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 12, 2008 9:25 AM
> To: solr-user@lucene.apache.org
> Subject: Re: upgrading to lucene
On Feb 12, 2008 9:25 AM, Robert Young <[EMAIL PROTECTED]> wrote:
> ok, and to do the change I just replace the jar directly in
> sorl/WEB_INF/lib and restart tomcat?
That should work.
-Yonik
ok, and to do the change I just replace the jar directly in
sorl/WEB_INF/lib and restart tomcat?
Thanks
Rob
On Feb 12, 2008 1:55 PM, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
> Solr Trunk is using the latest Lucene version. Also note there are a
> couple edge cases in Lucene 2.3 that are causin
Solr Trunk is using the latest Lucene version. Also note there are a
couple edge cases in Lucene 2.3 that are causing problems if you use
SOLR-342 with lucenAutoCommit == false.
But, yes, you should be able to drop in 2.3, as that is one of the
back-compatible goals for Lucene minor releas
