Hello,
I have trouble with writing and searching on lucene index same time,
all I did so far is making a class which has 2 methods:
private String indexLocation;
public void addDocument(int id,String title, String body) throws IOException{
IndexWriter indexWriter = new
Version 1.8 of VTD-XML is now released. The new features are:
·XMLModifier is a easy to use class that takes advantage of the
incremental update capability offered by VTD-XML
·XPath built-in functions are now almost complete
·This release added encoding support for
On 11/29/06, Java Programmer [EMAIL PROTECTED] wrote:
Hello,
I have trouble with writing and searching on lucene index same time,
all I did so far is making a class which has 2 methods:
private String indexLocation;
public void addDocument(int id,String title, String body) throws IOException{
I'm using lucene as a backend for my webservices that provide add,
remove and search operations. When I add or remove documents via
IndexModifier, I believe I'm supposed to close the IndexSearcher I
use for query requests. However, I cache Hits and I believe the
javadocs indicate closing
Chris,
Thanks so much both for the pointer and the sanity check!
Oddly enough, I read the same Syns2Index piece of documentation as you
suggested very early in the search process. What I did get wrong was
the actual download package, not realizing that *.java and *.class files
would not be
On 11/29/06, Eric Brown [EMAIL PROTECTED] wrote:
I'm using lucene as a backend for my webservices that provide add,
remove and search operations. When I add or remove documents via
IndexModifier, I believe I'm supposed to close the IndexSearcher I
use for query requests. However, I cache Hits
Hi Yonik,
On Nov 29, 2006, at 11:16 AM, Yonik Seeley wrote:
On 11/29/06, Eric Brown [EMAIL PROTECTED] wrote:
[snip]
Also, should I keep one IndexModifier open for the life of my
service/
application or should I open and close it when I get new requests to
add or remove documents? (I don't
On 11/29/06, Eric Brown [EMAIL PROTECTED] wrote:
IndexModifier currently has very low performance with mixed adds
and deletes.
You can keep the same one over the lifetime of the app though.
Assuming I call flush() after every operation (they won't be that
frequent), if I don't call close()
On 11/29/06, Yonik Seeley [EMAIL PROTECTED] wrote:
On 11/29/06, Eric Brown [EMAIL PROTECTED] wrote:
IndexModifier currently has very low performance with mixed adds
and deletes.
You can keep the same one over the lifetime of the app though.
Assuming I call flush() after every operation
If you haven't seen the following option you might want to check it out. It
uses reference counting to keep track of writers/searchers/etc(I think solr
does as well).
Has worked great for everything I have thrown at it other than need some tweaks
to its multisearcher support. Also is a good
On Tuesday 28 November 2006 23:09, Kai R. Emde wrote:
we have one problem with the sort routine. We use the multisearcher
function over severall index.
Does that also happens when you're not using MultiSearcher? Could you post
a small test case that demonstrates this problem? To my knowledge,
Michael McCandless wrote:
Van Nguyen wrote:
I'm running this on Windows 2003 server (NTFS). The Java VM version is
1.5.0_06. This exception is not consistent, but it is not intermittent
either. It does not throw it at any particular point while rebuilding
the index, but it will throw this
12 matches
Mail list logo
