Re: Searching with "1"

2006-10-03 Thread djd0383
After thinking through what was happening in Hits, I decided to see if catching a general exception would come back with anything. Although it can be argued that the code should have been doing this all along, that is a different story. So, I added Exception to the catch clauses, and it in fact

Re: Searching with "1"

2006-10-02 Thread djd0383
Fixed the issue... It turns out that I was going over TooManyClauses, and this decided to give an exception. I am not really sure of the reasoning behind this exception? It seems to us that it might be better to throw an exception. This way the programmer can handle this accordingly and will f

Re: Searching with "1"

2006-10-02 Thread djd0383
would this work but our classes - which are practically the same - not work? The only difference in your version and mine is that you switch the IndexReader with RAMDirectory. Any thoughts? Doron Cohen wrote: > > djd0383 <[EMAIL PROTECTED]> wrote on 25/09/2006 11:21:13: >>

Re: Upgrading 1.4 to 2.0 - Indexing Issue.

2006-10-02 Thread djd0383
Well I figured it out... After getting Luke I was able to see that the values were all being indexed correctly. The problem came when take the ids from the index and running it agains the database. It was in fact searching the db on the Lucene indices instead of the db index. A simple parse an

Re: Upgrading 1.4 to 2.0 - Indexing Issue.

2006-09-29 Thread djd0383
the FAQ also mentions this. Thank you for the idea. I think I will run this by the higher ups to see if I can do this task next. I hope this gives you a better idea of what I am trying to accomplish. Thank you for your help. Doron Cohen wrote: > > djd0383 <[EMAIL PROTECTED]>

Re: Upgrading 1.4 to 2.0 - Indexing Issue.

2006-09-29 Thread djd0383
t work": > - 'searchText' - the text of the field added to the document, that > should > be returned by the query but is not. > - 'search' - the query text, for the query that should find that > document, but does not. > - which analyzer is used at

Re: Upgrading 1.4 to 2.0 - Indexing Issue.

2006-09-29 Thread djd0383
query text, for the query that should find that > document, but does not. > - which analyzer is used at search > - which analyzer used at indexing > > > djd0383 <[EMAIL PROTECTED]> wrote on 29/09/2006 10:28:18: >> >> I am in the process of trying to upgrade to v2.0

Upgrading 1.4 to 2.0 - Indexing Issue.

2006-09-29 Thread djd0383
I am in the process of trying to upgrade to v2.0 from v1.4 and am having trouble building my index. For each of the various entries in the database, I am more or less doing the following: doc1.add(new Field("allText",searchText,Store.NO,Index.TOKENIZED)); indexWriter.add(doc1); This seems to bu

Re: Searching with "1"

2006-09-25 Thread djd0383
What are the Store and Index classes? It does not seem that my version of Lucene is using them Doron Cohen wrote: > > djd0383 <[EMAIL PROTECTED]> wrote on 25/09/2006 11:21:13: >> Those two message print the following: >> For qtxt 1* the result query is allText:1

Re: Searching with "1"

2006-09-25 Thread djd0383
Those two message print the following: For qtxt 1* the result query is allText:1* and The analyzer in use is: org.apache.lucene.analysis.standard.StandardAnalyzer - org.apache.lucene.analysis.standard.StandardAnalyzer I hope this helps. Thank you for all your help. Doron Cohen wrote: > > >

Re: Searching with "1"

2006-09-25 Thread djd0383
My QueryParser looks like this: query = QueryParser.parse("1*","allText",analyzer); analyzer is predetermited for this class. Is there something special I should be setting in this to allow for this search string? Thanks again! Doron Cohen wrote: > > djd0383 &l

Re: Searching with "1"

2006-09-25 Thread djd0383
The top of the stack was the stack I posted. I am not able to give the entire stack, but this is the important part. The exception is something about searching with null. When I say that I am searching for '1', the user is phyisically entering '1' into the search form and submitting. This sear

Re: Searching with "1"

2006-09-22 Thread djd0383
And why would Lucene be doing that now? That just doesn't seem to be the right thing to do. Yonik Seeley wrote: > > On 9/22/06, djd0383 <[EMAIL PROTECTED]> wrote: >> Also, I forgot to mention, but the error is throwing a message implying >> it >> cannot se

Re: Searching with "1"

2006-09-22 Thread djd0383
: > > What is the exception stack trace? > > djd0383 <[EMAIL PROTECTED]> wrote on 22/09/2006 16:07:53: >> >> I am managing a few Lucene searches in the application that I am > building. >> We have noticed that when a user searches with the string "1", this w

Searching with "1"

2006-09-22 Thread djd0383
I am managing a few Lucene searches in the application that I am building. We have noticed that when a user searches with the string "1", this will throw an exception. The search works fine until Lucene tries to build its Hits. Is there any reason why this would be true? Also, what is a common