RE: NFS/iSCSI SAN with Lucene

Hi Mike, Thanks for the information! Peter > -Original Message- > From: Michael McCandless [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 19, 2006 5:49 PM > To: java-user@lucene.apache.org > Subject: Re: NFS/iSCSI SAN with Lucene > > > > I did a search on the Lucene list archives,

NFS/iSCSI SAN with Lucene

Hi, I did a search on the Lucene list archives, found a lot of posts about the use of Lucene with NFS and how there are locking issues, but don't see anybody coming to a real solution to this. Here's the most promising thread I found: http://www.gossamer-threads.com/lists/lucene/java-user/8302?sea

RE: Lucene Index Changed event

You can check IndexReader.getCurrentVersion() to see if the index changed from the last time you checked. The index's version number changes whenever the index is updated. Peter > -Original Message- > From: Aigner, Thomas [mailto:[EMAIL PROTECTED] > Sent: Monday, November 21, 2005 3:48 P

RE: Analysis

Ok... just got confused because you mentioned XML. Unless you're actually indexing the raw XML in some of your fields, the fact that you're indexing XML documents as your source content is irrelevant to your choice of Analyzer. Choice of indexer really depends on your specific project requirements

RE: Analysis

Not exactly sure what you're asking with regards to Analyzers and parsing XML... But for parsing and indexing XML documents with Lucene, you can find a lot of material out there by searching the list archives and using google. However, the document I found most helpful was this piece written by Ot

RE: Indexing

You need to delete the document from the index and reindex it. This is in the LuceneFAQ: http://wiki.apache.org/jakarta-lucene/LuceneFAQ#head-917dd4fc904aa20a34e bd23eb321125bdca1dea2 (or #24 under 3. Indexing) Peter > -Original Message- > From: anushri kumar [mailto:[EMAIL PROTECTED]

RE: Help requested

I just wanted to clarify... I don't believe the following statement is accurate: > > The "contents" field searches on the entire document, > including all indexes. There is no default field named "contents" that automatically combines the contents of all your fields. As Erik mentioned, you nee

RE: How to combine multiple fielded queries in Lucene

If you're using the QueryParser, you just prefix the field-specific part with the field. For example, the query in your email should be submitted to the query parser as: (Title:"baseball" OR Summary:"white sox") AND Publication_date:"199501 TO 200412" or if you're creating is programmatically, th

RE: Delete doesn't delete?

Are you using a hit collector? I think if you use a hit collector rather than the Hits object for getting query results, deleted items will still be returned as results. My workaround for this was to run optimize after I finish a batch of deletes, which works fine for my system because I only run a

RE: RemoteSearchable woes

The system I'm working on requires that I also need to use a custom hit collector. I'm not using the RemoteSearchable. Instead, I'm just binding an object called SearcherImpl that contains an IndexSearcher and a getResults() method that uses the custom hit collector. Peter > -Original Messag

RE: Re: Lucene and remote index and java applet, with no java app server

I'm not sure about Perl or PHP--perhaps there are some ports of Lucene that'll let you do that. But the most straightforward way is to just write a simple Java web application with a servlet that uses an IndexSearcher to execute a form-entered query and have it return results. It seems like you m

RE: IllegalArgumentException: attempt to access a deleted document

I think my best option will just be to optimize the index after each deletion. I guess this will be good for me anyways... For the cases where optimizing is not a luxury one can afford, it would be nice if there was another way around this. Peter > -Original Message- > From: Pet

IllegalArgumentException: attempt to access a deleted document

Hi, I'm getting this error from trying to access a document in my custom hit collector: java.lang.IllegalArgumentException: attempt to access a deleted document at org.apache.lucene.index.SegmentReader.document(SegmentReader.java:235 ) at org.apache.lucene.index.MultiReader.docume

IndexSearcher architecture and memory usage

y consumption by an IndexSearcher object is proportional to the size of the index, is there any downside to splitting up a single large index into up to 30 different indexes? I would really appreciate your help. Thanks! Peter - Peter Kim [EMAIL PROTECTED]

Problem with deleting and optimizing index

Hi all, I have a problem related to index size and deleting and optimizing. So from reading various sources online, it seems as though the size of the Lucene index should become no larger than half the size of the disk since during optimization, the size of the index can ballon to double the origi

issues with concurrent indexing and searching with HitCollector

Hi, I did a quick google search and couldn't find any info on this... I seem to be having a problem when I try to execute a search using a HitCollector while the index is being indexed. Does it make sense that I could be getting this error because the index is being merged while the HitCollector i

issues with concurrent indexing and searching with HitCollector

k.java:109) org.apache.lucene.index.IndexReader.open(IndexReader.java:111) org.apache.lucene.index.IndexReader.open(IndexReader.java:95) org.apache.lucene.search.IndexSearcher.(IndexSearcher.java:38) Thanks! peter ----- Peter Kim Software Engineer [EMAIL PROTECTED] Cymfony