On Thursday 25 May 2006 22:14, wenjie zheng wrote:
> I followed the instruction in wiki and generated an patch file, which I
> attach to this email.
> But I did not find where to upload this patch file in JIRA bug report.
Only after the JIRA issue has been created, a file can be attached.
For an
You have to fill in the fields provided and finish up the two steps to
insert the bugreport. When you have finished your report you can
upload your file as an attachment to the report.
It's on the left hand side of your screen "operations --> attache file
to this issue"
simon
On 5/25/06, wenjie
I followed the instruction in wiki and generated an patch file, which I attach to this email.But I did not find where to upload this patch file in JIRA bug report.Can someone help me?
On 5/17/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: I put Lock in IndexReader.indexExists function, and testes
: I put Lock in IndexReader.indexExists function, and testes for a few days
: It worked fine. I never had that mistery problem.
:
: How can put the patch in a JIRA issue?
Please take a look at the recently added FAQ "How do I contribute an
improvement?"...
http://wiki.apache.org/jakarta-lucene/L
he.org
Sent: Tuesday, May 9, 2006 10:57:05 AM
Subject: Re: weird behavior of IndexReader.indexExists()
I am a little bit confused here.
Since I didn't change the lock directory or disable locking and it is on
the
single server sharing same fs, does it mean I am not supposed to get the
erro
m: wenjie zheng <[EMAIL PROTECTED]>
To: java-dev@lucene.apache.org
Sent: Tuesday, May 9, 2006 10:57:05 AM
Subject: Re: weird behavior of IndexReader.indexExists()
I am a little bit confused here.
Since I didn't change the lock directory or disable locking and it is on the
single server shari
s typically /tmp under
UNIX/OSX and C:\WINDOWS\TEMP (I think) on Winblows.
Otis
- Original Message
From: wenjie zheng <[EMAIL PROTECTED]>
To: java-dev@lucene.apache.org
Sent: Tuesday, May 9, 2006 9:09:47 AM
Subject: Re: weird behavior of IndexReader.indexExists()
Thanks,
I guess
ally /tmp under UNIX/OSX and
C:\WINDOWS\TEMP (I think) on Winblows.
Otis
- Original Message
From: wenjie zheng <[EMAIL PROTECTED]>
To: java-dev@lucene.apache.org
Sent: Tuesday, May 9, 2006 9:09:47 AM
Subject: Re: weird behavior of IndexReader.indexExists()
Thanks,
I guess my questio
ei 2006 13:47
To: java-dev@lucene.apache.org
Subject: RE: weird behavior of IndexReader.indexExists()
Hi
I think I have discovered this too.
It is on my list of issues to raise
The index exist test looks for the segment file.
When the index is committing, and you are unlucky, this file m
een patched
a couple of months ago.
Luc
-Original Message-
From: Andy Hind [mailto:[EMAIL PROTECTED]
Sent: dinsdag 9 mei 2006 13:47
To: java-dev@lucene.apache.org
Subject: RE: weird behavior of IndexReader.indexExists()
Hi
I think I have discovered this too.
It is on my list of issues
exist.
Regards
Andy
-Original Message-
From: wenjie zheng [mailto:[EMAIL PROTECTED]
Sent: 08 May 2006 18:57
To: java-dev@lucene.apache.org
Subject: Re: weird behavior of IndexReader.indexExists()
This happens sometimes when number of docs is over 2000. So it's kinda
of
random.
Wenji
This happens sometimes when number of docs is over 2000. So it's kinda of
random.
Wenjie
On 5/8/06, wenjie zheng <[EMAIL PROTECTED]> wrote:
I created an index with more than 30,000 text files.
I used indexExists() to determine either to create a new index or to add
docs to the existing index.
12 matches
Mail list logo
