INDEXREADER + MAXDOC

2005-01-04 Thread Karthik N S
Hi Guys Apologies... On using the integer number of Indexreader.maxDoc() API , Is it possible to get the VALUES from the varoius fieldtypes. ex:- 'docs.get(contents) at IndexReader.maxdoc()' If so How...?? WITH WARM REGARDS HAVE A NICE DAY [ N.S.KARTHIK]

Re: INDEXREADER + MAXDOC

2005-01-04 Thread Erik Hatcher
On Jan 4, 2005, at 5:19 AM, Karthik N S wrote: On using the integer number of Indexreader.maxDoc() API , Is it possible to get the VALUES from the varoius fieldtypes. ex:- 'docs.get(contents) at IndexReader.maxdoc()' If so How...?? Just to be sure I understand... you want the last document

RE: INDEXREADER + MAXDOC

2005-01-04 Thread Karthik N S
Hi Erik Apologies... I would like to EXTRACT the DATA from the various fields of the Last Document [as u said ] Ex: at IndexReader.maxDoc = 100 doc.get(Content) == ISBN100 doc.get(name)== LUCENE IN ACTION doc.get(author) == Erik Hatcher . This is my

Re: INDEXREADER + MAXDOC

2005-01-04 Thread Erik Hatcher
On Jan 4, 2005, at 7:29 AM, Karthik N S wrote: Hi Erik I would like to EXTRACT the DATA from the various fields of the Last Document [as u said ] Ex: at IndexReader.maxDoc = 100 doc.get(Content) == ISBN100 doc.get(name)== LUCENE IN ACTION doc.get(author) == Erik Hatcher

lucenebook.com

2005-01-04 Thread Erik Hatcher
Otis and I have been working hard to get a website up for Lucene in Action and beyond. It's finally in place at: http://www.lucenebook.com We haven't put in place as much explanation and help there as we should, and I'm sure by opening up the flood gates on it we'll uncover issues

Re: Deleting an index

2005-01-04 Thread Luke Shannon
If you opened an IndexReader was has it also been closed before you attempt to delete? - Original Message - From: Scott Smith [EMAIL PROTECTED] To: lucene-user@jakarta.apache.org Sent: Monday, January 03, 2005 7:39 PM Subject: Deleting an index I'm writing some junit tests for my

Problems...

2005-01-04 Thread Ross Rankin
(Bear with me; I have inherited this system from another developer who is no longer with the company. So I am not familiar with Lucene at all. I just have got the task of Fixing the search.) I have servlet that runs every 10 minutes and indexes and I can see files being created in the

Re: Problems...

2005-01-04 Thread Luke Shannon
I had a similar situation with the same problem. I found the previous system was creating all the object (including the Searcher) and than updating the Index. The result was the Searcher was not able to find any of the data just added to the Index. The solution for me was to move the creation

1.4.3 breaks 1.4.1 QueryParser functionality

2005-01-04 Thread Bill Janssen
I'm trying to figure out what changed between 1.4.1 and 1.4.3 to break my application. I couldn't use 1.4.2, because my app wouldn't compile with 1.4.2, due to API changes. With 1.4.3, the API incompatibilities were fixed, but now the QueryParser seems to process query strings differently. For

how to create a long lasting unique key?

2005-01-04 Thread Peter Veentjer - Anchor Men
What is the best way to create a key for a document? I know the id (from hits) can not be used, but what is a good way to create a key I need this key for a webapplication. At the moment every document can be identified with the filelocation key, but I would rather some kind of integer for the

Re: how to create a long lasting unique key?

2005-01-04 Thread PA
On Jan 04, 2005, at 20:43, Peter Veentjer - Anchor Men wrote: What is the best way to create a key for a document? UUID? http://java.sun.com/j2se/1.5.0/docs/api/java/util/UUID.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For

Re: how to create a long lasting unique key?

2005-01-04 Thread Luke Shannon
This is taken from the example code writen by Doug Cutting that ships with Lucene. It is the key our system uses. It also comes in handy when incrementally updating. Luke public static String uid(File f) { // Append path and date into a string in such a way that lexicographic // sorting

Re: Problems...

2005-01-04 Thread Erik Hatcher
On Jan 4, 2005, at 10:53 AM, Ross Rankin wrote: I'm not sure where or how to troubleshoot. Can I examine the indexes with anything to see what is there and that it's meaningful. Is there something simple I can do to track down what doesn't work in the process? Thanks. Echoing a previous

Parsing issue

2005-01-04 Thread Hetan Shah
Hello All, Does any one know how to handle the following parsing error? thanks for pointers/code snippets. -H While trying to parse a HTML file using IndexHTML I get Parse Aborted: Encountered \ at line 8, column 1162. Was expecting one of: ArgName ... = ... TagEnd ...

Re: 1.4.3 breaks 1.4.1 QueryParser functionality

2005-01-04 Thread Erik Hatcher
Bill, If we broken API compatibility then we screwed up. What getFieldQuery signature are you overriding? As for version numbers - there are no strict conventions. The API should not have broken in 1.4.2, nor in 1.4.3 - this is very unfortunate. I caught what I thought were all of the

Re: Parsing issue

2005-01-04 Thread Erik Hatcher
Sure... clean up your HTML and it'll parse fine :) Perhaps use JTidy to clean up the HTML. Or switch to using a more forgiving parser like NekoHTML. Erik On Jan 4, 2005, at 3:59 PM, Hetan Shah wrote: Hello All, Does any one know how to handle the following parsing error? thanks for

Re: Parsing issue

2005-01-04 Thread Hetan Shah
Has any one used NekoHTML ? If so how do I use it. Is it a stand alone jar file that I include in my classpath and start using just like IndexHTML ? Can some one share syntax and or code if it is supposed to be used programetically. I am looking at http://www.apache.org/~andyc/neko/doc/html/

Re: Parsing issue

2005-01-04 Thread Otis Gospodnetic
That's the correct place to look and it includes code samples. Yes, it's a Jar file that you add to the CLASSPATH and use ... hm, normally programmatically, yes :). Otis --- Hetan Shah [EMAIL PROTECTED] wrote: Has any one used NekoHTML ? If so how do I use it. Is it a stand alone jar

Re: 1.4.3 breaks 1.4.1 QueryParser functionality

2005-01-04 Thread Bill Janssen
Erik, The signature I'm overriding is protected Query getFieldQuery (String field, Analyzer a, String queryText) throws ParseException It gets called with a query string of the form field:text but no longer

Re: 1.4.3 breaks 1.4.1 QueryParser functionality

2005-01-04 Thread Daniel Naber
On Tuesday 04 January 2005 23:53, Bill Janssen wrote: protected Query getFieldQuery (String field, Analyzer a, String queryText) throws ParseException You're right, the problem is that we should call the deprecated method for example in

Re: 1.4.3 breaks 1.4.1 QueryParser functionality

2005-01-04 Thread Bill Janssen
You're right, the problem is that we should call the deprecated method for example in getFieldQuery(String field, String queryText, int slop). However, there's a simple workaround: just remove the analyzer parameter from your method. Sure, if I wanted to ship different code for each

Re: Problems...

2005-01-04 Thread Chris Hostetter
To start with, there has to be more to the search side of things then what you included. this search function is not static, which means it's getting called on an object, which obviously has some internal state (paramOffset, hits, and pathToIndex are a few that jump out at me) what are the

RE: Parsing issue

2005-01-04 Thread Chuck Williams
I use it and have yet to have a problem with it. It uses the Xerces API so you parse and access html files just like xml files. Very cool, Chuck -Original Message- From: Otis Gospodnetic [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 04, 2005 2:05 PM To: Lucene Users List

Re: 1.4.3 breaks 1.4.1 QueryParser functionality

2005-01-04 Thread Bill Janssen
However, there's a simple workaround: just remove the analyzer parameter from your method. Sure, if I wanted to ship different code for each micro-release of Lucene (which, you might guess, I don't). That signature doesn't compile with 1.4.1. Bill Let me be a bit more explicit. My