Got it :)
Thanks for the link.
[closed]
On Sat, Apr 2, 2011 at 6:14 AM, Koji Sekiguchi [via Lucene] <
ml-node+2765616-1923995541-376...@n3.nabble.com> wrote:
> (11/04/01 21:32), shrinath.m wrote:
> > I was wondering whats the difference between the Lucene's 2
> implementation of
> > highlighter
(11/04/01 21:32), shrinath.m wrote:
I was wondering whats the difference between the Lucene's 2 implementation of
highlighters...
I saw the javadoc of FVH, but it only says "another implementation of Lucene
Highlighter" ...
Description section in the javadoc shows the features of FVH:
https://
On Sat, Apr 2, 2011 at 7:07 AM, Christopher Condit wrote:
> I see in the JavaDoc for IndexWriterConfig that:
> "Note that IndexWriter makes a private clone; if you need to
> subsequently change settings use IndexWriter.getConfig()."
>
> However when I attempt to use the same IndexWriterConfig to c
The issue is that a MergePolicy instance cannot be re-used across
multiple writers.
So, you could take your first IWC, change out the MergePolicy, then re-use it?
Other things also cannot be reused, eg a ConcurrentMergeScheduler instance.
Mike
http://blog.mikemccandless.com
On Fri, Apr 1, 2011
I see in the JavaDoc for IndexWriterConfig that:
"Note that IndexWriter makes a private clone; if you need to
subsequently change settings use IndexWriter.getConfig()."
However when I attempt to use the same IndexWriterConfig to create
multiple IndexWriters the following exception is thrown:
org.
2011/4/1 Yogesh Dabhi :
> Hi
>
> Concurrently 5 user access same lucene directory for searching document
>
> That time I got bellow exception
>
> org.apache.lucene.store.AlreadyClosedException: this IndexReader is
> closed
>
> is there a way to handle such error
Use a ReentrantReaderWriterLock aro
Hi
Concurrently 5 user access same lucene directory for searching document
That time I got bellow exception
org.apache.lucene.store.AlreadyClosedException: this IndexReader is
closed
is there a way to handle such error
Thanks & Regards
Yogesh
You might consider a multiValued field and a positionIncrementGap longer
than the longest tuple.
At that point, you can search for phrase queries where the slop is less than
the positionIncrementGap.
I'm a bit rushed, so if you need more details we can talk later
Best
Erick
2011/4/1 袁武 [GMa
Solr has a hyphenated word filter you could copy.
http://lucene.apache.org/solr/api/org/apache/solr/analysis/HyphenatedWordsFilterFactory.html
On trunk, this has been folded into the analysis module.
-Yonik
http://www.lucenerevolution.org -- Lucene/Solr User Conference, May
25-26, San Francisco
Don't prefix queries get rewritten wrapped in ConstantScoreQuery,
meaning all will get the same score and you get them in read order?
Checking the API, PrefixQuery uses
MultiTermQuery.CONSTANT_SCORE_AUTO_REWRITE_DEFAULT, which can be changed
with setRewriteMethod.
-Original Message-
From:
Hmm so it's not index corruption. Curious.
Which Lucene version are you using? Looks like it's 2.9, but not
2.9.4? Can you try 2.9.4 and see if you still hit the problem?
Can you post a small test case showing the problem, on your index?
Mike
http://blog.mikemccandless.com
2011/4/1 袁武 [GMai
>> Ideally I'd like to have the parser use the
>> custom analyzer for everything unless it's going to parse a clause into
>> a PhraseQuery or a MultiPhraseQuery, in which case it uses the
>> SimpleAnalyzer and looks in the _exact field - but I can't figure out
>> the best way to accomplish this.
>
Hi,
for indexing PDF files we have to undo word hyphenation. The basic idea
is simply to remove the hyphen when a new line and a small letter
follows. Of course this approach isnt 100%-foolproofed but checking
against a dictionary wouldnt be as well...
Since we face this problem too when hig
Probably a bug in your code.
If you post again with, as a minimum, the version of lucene that you
are using and your search/sort code, you might get a better answer.
Best of all would be a complete self-contained standalone program or
test case that demonstrates the problem.
--
Ian.
On Fri, Ap
Hi,
I know the default is sort by relevance. While, when i search the prefix
(interface*), it does not work. It can only sort the document by the order of
reading files.
What is the problem???
Thx.
I was wondering whats the difference between the Lucene's 2 implementation of
highlighters...
I saw the javadoc of FVH, but it only says "another implementation of Lucene
Highlighter" ...
Can someone throw some more light on this ?
--
View this message in context:
http://lucene.472066.n3.nabbl
or maybe MemoryIndex (in contrib) is more suited to what he wants
On Fri, Apr 1, 2011 at 1:10 PM, Ian Lea wrote:
> RAMDirectory. The clue is in the name ...
>
>
> --
> Ian.
>
>
> On Fri, Apr 1, 2011 at 11:08 AM, Patrick Diviacco
> wrote:
> > Is there a way to index data into memory without wr
> Sorry I am using 2.9.4, which is the same as 3.0.3?
Not by my definition of "the same".
> The code below demonstrates the problem.
Not really. I'd be more convinced if it compiled. And how can we be
sure the docs are exactly as you say? That you are actually executing
the span queries you h
Sorry, I have got this working now. It was a silly mistake.
-Original Message-
From: Gregory Tarr [mailto:gregory.t...@detica.com]
Sent: 01 April 2011 12:13
To: java-user@lucene.apache.org
Subject: RE: SpanNearQuery with repeated term?
Sorry I am using 2.9.4, which is the same as 3.0.3?
Sorry I am using 2.9.4, which is the same as 3.0.3?
The code below demonstrates the problem.
Thanks
Greg
-Original Message-
From: Ian Lea [mailto:ian@gmail.com]
Sent: 01 April 2011 12:10
To: java-user@lucene.apache.org
Subject: Re: SpanNearQuery with repeated term?
I can't reprod
RAMDirectory. The clue is in the name ...
--
Ian.
On Fri, Apr 1, 2011 at 11:08 AM, Patrick Diviacco
wrote:
> Is there a way to index data into memory without writing to disk in Lucene ?
>
> This is my current code storing it on disk
>
> writer = new IndexWriter(FSDirectory.open(index_dir), ne
I can't reproduce this using lucene-core-3.0.3.jar. You don't say
what version you are using. Why don't you post the smallest possible
complete standalone program or test case that demonstrates the
problem. And tell us what version of lucene you are working with.
Always.
--
Ian.
On Fri, Apr
I am having some issues with SpanNearQuery:
SpanQuery[] clauses = new SpanTermQuery[2];
Clauses[0] = new SpanTermQuery("text","");
Clauses[1] = new SpanTermQuery("text","");
SpanNearQuery q = new SpanNearQuery(clauses,0,true); // returns 1
document with " " in it
SpanQuery[] claus
Hi, Dear Mike:
belows list the report of checkIndex. OS is Fedora Linux.
[oracle@server bin]$ java -classpath ./ org.apache.lucene.index.CheckIndex
/data/Index/URL/Generic/ -fix
NOTE: testing will be more thorough if you run java with
'-ea:org.apache.lucene...', so assertions are enabled
Openi
Is there a way to index data into memory without writing to disk in Lucene ?
This is my current code storing it on disk
writer = new IndexWriter(FSDirectory.open(index_dir), new
IndexWriterConfig(org.apache.lucene.util.Version.LUCENE_40, new
WhitespaceAnalyzer(org.apache.lucene.util.Version.LUCEN
Hmm this could be from a corrupted index.
What version of Lucene? What OS/filesystem?
Can you run CheckIndex and post the output?
Mike
http://blog.mikemccandless.com
2011/3/31 袁武 [GMail] :
> Hi, dear experts:
>
> When IndexReader.termsPositions is used to access specific terms, the call to
>
Hi Wouter,
See point 8 in the Backwards Compatibility CHANGES.txt. The reason is
explained in several issues (not all listed there), problems are e.g. in the
Unicode 4 changes, where a non-final WhitespaceTokenizer would need to do
reflection-based backwards hacks (like in 2.9 when we changed to
i
I'm doing the upgrade to Lucene 3.1.0.
The upgrade failed on WhitespaceTokenizer being final in this version.
I don't understand why anyone would make this tokenizer final, I was
happlily extending it for many Lucene versions!
Wouter
-
28 matches
Mail list logo
