Hi all,
I am new to lucene. I would like to know if there can be any performance
issues if we update the boost of a document often. Does this scale linearly
with index size?
Hi,mark
You are right ,using accessor.release(indexwriter) avoid throwing the
indexwriter closed exception .
Thanks.
kai
-邮件原件-
发件人: Mark Miller [mailto:[EMAIL PROTECTED]
发送时间: 2007年8月7日 星期二 19:10
收件人: java-user@lucene.apache.org
主题: Re: 答复: 答复: About muti-Threads in Lucene
You don't c
Nutch uses it's own Analyzer. You should use the Analyzer that Nutch
uses in order to get proper results. That may mean adding the Nutch
Analyzer to your Luke classpath.
-Grant
On Aug 7, 2007, at 7:22 PM, Kai_testing Middleton wrote:
I'm invoking Luke like this:
java -jar lukeall-0.7.
>From the documentation for both SimpleAnalyzer and
StopAnalyzer...
...with LowerCaseFilter...
So I assume that your problem is the capital "N"...
Erick
On 8/7/07, Kai_testing Middleton <[EMAIL PROTECTED]> wrote:
>
> I'm invoking Luke like this:
>java -jar lukeall-0.7.1.jar
> I run this que
I'm invoking Luke like this:
java -jar lukeall-0.7.1.jar
I run this query:
content:Nyarubuye
When I use the StandardAnalyzer I get results but when I use the
KeywordAnalyzer I don't get results. Can someone explain this?
My corpus was crawled and indexed using a nightly build of nutch (
Check out Filter class. You can create a separate filter for each field and
then chain them together using ChainFilter. If you cache the filter, it will
be pretty fast.
Chew Yee Chuang wrote:
>
> Greetings,
>
> Yes, process a little bit and stop for a while really reduce the CPU
> usage,
> bu
"SK R" <[EMAIL PROTECTED]> wrote:
> Hi,
> Thanks for this valuable informations.
> I'm using Lucene2.1 now. Do I need to apply the patch "LUCENE-843"
> with
> existing one or i have to move the latest?
It's probably best to use a nightly build JAR of Lucene to play with
LUCENE-843.
You don't close the indexwriter (or readers or searchers) with the
accessor code. You release them, and the accessor code will close them
when appropriate.
- Mark
Kai Hu wrote:
> Hi,Patrick
> I tested use a map , get a single LuceneIndexAccessor,and get a cached
> IndexWriter ,but after do
Greetings,
Yes, process a little bit and stop for a while really reduce the CPU usage,
but I need to find out a balance so that the indexing or searching will not
have so much delay.
Execute 20,000 queries at a time is because the process is generating the
aggregation data for reporting,
E.g Gend
Hi,
Thanks for this valuable informations.
I'm using Lucene2.1 now. Do I need to apply the patch "LUCENE-843" with
existing one or i have to move the latest? Do i need to use flushByRam
instead of flushbydoc to work with this patch?
Regards
RSK
On 8/7/07, Michael McCandless <[EMAIL PROT
Hi Patrick
Thanks for your soonest reply these days.
Luke is convenient to query the data .
Thanks again.
kai
--
> Hi Kai
>
> No, I have no problem returning hits.
>
> When I do have problems like this, I usually find I have something
> more to learn about L
"Mike Klaas" <[EMAIL PROTECTED]> wrote:
> > On 8/6/07, testn <[EMAIL PROTECTED]> wrote:
> >>
> >> 2. To improve indexing speed, you can consider using the trunk
> >> code which
> >> includes LUCENE-843. The indexing speed will be faster by almost
> >> an order of
> >> magnitude.
>
> While a
Hi Kai
No, I have no problem returning hits.
When I do have problems like this, I usually find I have something
more to learn about Lucene indexing. Try looking at the data and
query in Luke. I usually find this is the best way to understand what
is going on.
Here is the link to Luke:
http://w
Hi, Hoss
when do add,update,delete operations in muti-threads,we should execute
IndexWriter.close() to release the Lock ,How do you control it to avoid Lucene
throw an Exception of "this IndexWriter is closed".Thanks.
kai
>
>: How do you solve the problems when add,update,del
14 matches
Mail list logo
