Also, I am not sure about the following below statement:
>>A direct update from 2.x to 4.0 is not possible
Are you saying that its impossible to upgrade from 2.4 - 4.0 version? Why
can't we upgrade? Any technical limitations with Lucene that will not allow
from upgrading from 2.4 - 4.x?.
I am d
We are upgrading from 2.4 - 4.0? What are the options here? ( To delete the
existing index directories and reindex with the upgraded ones).
We don't want to take any intermediate steps which would cause more work
again to upgrade to the latest version.
Thanks,
Sai.
--
View this message in cont
You have to update in 1 extra steps: 2.x -> 3.6.2 and then you can use the
index in 4.0, because it can read 3.x indexes. To upgrade to Lucene 3.6,
download lucene-core-3.6.2.jar and run:
$ java -cp lucene-core-3.6.2.jar org.apache.lucene.index.IndexUpgrader
After that the binary index format
Hi,
That'a the way to go! With this method, you don't need to use FilteredQuery, it
is done under the hood automatically.
Please take care that Collector works, in contrast to HitCollector, per index
segment (setScorer/setNextReader), so you have to rewrite at least most of you
collection code
Thanks.
Can we use the following method in 4.0 as a replacement for the above
method? However, we will rewrite this to use FilteredQuery later but don't
want to refactor a lot.
public void search(Query query,
Filter filter,
Collector results)
throws IOException
ht
Hi,
the methods taking Weight are not for public use, only for internal use (e.g.
subclasses). You should not pass Weight to IndexSearcher, use the native Query
instance! Why do you want to pass a Weight to IndexSearcher?
Every Weight is created by a Query instance, so you can always pass the
We are using the following below method with Lucene 2.4.0
public void search(Weight weight,
Filter filter,
HitCollector results)
throws IOException
We are upgrading to the latest version and looking at the API (4.0), the
above signature has been d
I've found a simpler subclass, that illustrates the same problem
package org.musicbrainz.search.analysis;
import org.apache.lucene.analysis.*;
import java.io.IOException;
import java.io.Reader;
/**
* For analyzing catalogno so can compare values containing spaces with
values that do not
*
January 2013, Apache Lucene⢠4.1 available
The Lucene PMC is pleased to announce the release of Apache Lucene 4.1.
Apache Lucene is a high-performance, full-featured text search engine
library written entirely in Java. It is a technology suitable for nearly
any application that requires full-text
On Mon, Jan 21, 2013 at 11:20 PM, Shai Erera wrote:
> (unfortunately, there's still no tool in Lucene to do that for you).
I think we should open an issue to provide support for distributed faceting?
For example, we already provide support for distributed searching
(TopDocs.merge), and distribu
Can you post the full stack trace of the CorruptIndexException?
Mike McCandless
http://blog.mikemccandless.com
On Tue, Jan 22, 2013 at 8:20 AM, Cheng wrote:
> Hi,
>
> I run a Lucene application on Tomcat. The app will try to open a Linux
> directory, and sometime returns CorruptIndexException e
I've been investigating potential memory leaks in my Lucene based
application thats runs on jetty. I did a memory dump with jmap and one
thing I've noticed is that for any subclass of analyzer that I have
created that there are alot instances of the $SavedStream inner class.
So for example I c
Yes, the release is wrapping up. I believe that an announcement message
will be sent in the coming days.
Shai
On Tue, Jan 22, 2013 at 2:51 PM, Nicola Buso wrote:
> I will try it.
>
> I see there is already a lucene-4.1.0 package (dated 2013/01/21)
> available for download, do you know if this
I will try it.
I see there is already a lucene-4.1.0 package (dated 2013/01/21)
available for download, do you know if this version will be released
soon?
Nicola.
On Tue, 2013-01-22 at 06:20 +0200, Shai Erera wrote:
> Hi Nicola,
>
> What I had in mind is something similar to this, which is pos
I havent started working on this yet. I use the LogByteSizeMergePolicy
because of personal reasons that have nothing to do with replication.
I havent found a lucene replication method. (?)
>From my research, there are 2 ways to replicate an index.
a) You stop indexing. You make a "hard" commit an
15 matches
Mail list logo