for your help Doron. You advice helped me a lot.
--
View this message in context:
http://www.nabble.com/modify-existing-non-indexed-field-tf1905726.html#a5324779
Sent from the Lucene - Java Users forum at Nabble.com.
-
To un
> can't access the file:
> http://cdoronc.20m.com/tmp/indexingThreads.zip
Yes, this Web host sometimes behaves strange when clicking a link from a
mail program. Please try to copy
cdoronc.20m.com/tmp
to the Web Browser (e.g. Firefox), click .
This should show the content of that tmp folder, inc
http://www.nabble.com/modify-existing-non-indexed-field-tf1905726.html#a5304328
Sent from the Lucene - Java Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> I did clean everything but still getting the same problem. I'm using
lucene
> 2.0. Do you get the same problem on your machine?
Please try with this code - http://cdoronc.20m.com/tmp/indexingThreads.zip
Regards,
Doron
-
To un
I did clean everything but still getting the same problem. I'm using lucene
2.0. Do you get the same problem on your machine?
--
View this message in context:
http://www.nabble.com/modify-existing-non-indexed-field-tf1905726.html#a5288759
Sent from the Lucene - Java Users forum at Nabbl
> I've tried changing to one indexing thread
> (instead of 5) but still get the same problem. can't figure out why this
> happens.
The program as listed seems to accesss an existing index - since 'create'
is always for both 'FSDirectory.getDirectoy(,)' and 'new
IndexWriter(,,)'. Perhaps an old lo
Thanks for your advice Doron. I've tried changing to one indexing thread
(instead of 5) but still get the same problem. can't figure out why this
happens.
--
View this message in context:
http://www.nabble.com/modify-existing-non-indexed-field-tf1905726.html#a5266343
Sent from the Luc
The lock time out exception is caused by trying to open multiple
IndexWriter objects in parallel - each of the 5 threads is creating its own
IndexWriter object in each invocation of addAndIndex(). This cannot work -
I think that chapter 2.9 of "Lucene in Action" is essential reading for
fixing this
exEntity.search("name:Nick" + i);
Thread.sleep(20);
}
}
catch (Exception e)
{
e.printStackTrace();
}
}
}
}
--
View this message in context:
http://www.nabble.com/modify-existing-non-indexed-fiel
> The problem I've had before was that I set my writer to null
> right after close it. That's why I got lock timeout exception
> when i try to create a the writer again. Guess I just need
> to close it, and re-open it would avoid the
> locking problems then.
It is valid to nullify the just closed
g problems then.
Thanks.
--
View this message in context:
http://www.nabble.com/modify-existing-non-indexed-field-tf1905726.html#a5239040
Sent from the Lucene - Java Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL
> From what you said, I'm thinking of switching to IndexModifier.
Yes, IndexModifier would synchronize add/delete. One should notice the
performance comment in IndexModifier
http://lucene.apache.org/java/docs/api/org/apache/lucene/index/IndexModifier.html
- "While you can freely mix calls to add
e's ids?
--
View this message in context:
http://www.nabble.com/modify-existing-non-indexed-field-tf1905726.html#a5229084
Sent from the Lucene - Java Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
On Samstag 08 Juli 2006 00:03, dan2000 wrote:
> When you do re-index, you'll have to close the reader, which
> would pause the search. Any better way of doint it?
Try using IndexModifier (added in Lucene 1.9).
Regards
Daniel
--
http://www.danielnaber.de
--
> dan2000 <[EMAIL PROTECTED]> wrote on 07/07/2006 15:03:35:
> but if you remove it and add it again, you'll need to re-index it again.
> don't you? When you do re-index, you'll have to close the reader, which
> would pause the search. Any better way of doint it?
INHO yes and no -
There's no need
but if you remove it and add it again, you'll need to re-index it again.
don't you? When you do re-index, you'll have to close the reader, which
would pause the search. Any better way of doint it?
--
View this message in context:
http://www.nabble.com/modify-existing-non-indexed-
: java-user@lucene.apache.org
Sent: Friday, July 7, 2006 6:54:18 AM
Subject: modify existing non-indexed field
Is it possible to modify a stored field but not indexed? for example, if I
have a field like this:
new Field("address", address, Field.Store.YES, Field.Index.NO)
and I want to mod
I don't think you've done anything to the index. This code is really
equivalent to something like
Field field = hits.doc(i).getField('address");
field.set("11 Diana Street");
You've changed the value of the field instance, but that is essentially a
local variable (even though not explicit in you
ible?
--
View this message in context:
http://www.nabble.com/modify-existing-non-indexed-field-tf1905726.html#a5215244
Sent from the Lucene - Java Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
19 matches
Mail list logo
