Re: Query across multiple fields scenario not handled by MultiFieldQueryParser

2004-07-19 Thread Daniel Naber
On Sunday 18 July 2004 18:39, Thomas Plümpe wrote: Does anybody here know which changes I would have to make to QueryParser.jj to get the functionality described? I haven't tried it but I guess you need to change the getXXXQuery() methods so they return a BooleanQuery. For example,

Re: Searching against Database

2004-07-19 Thread Gerard Sychay
You might run into problems with having too many Fields by treating each record as a Document and each column as a Field in that Document. An alternative would be to index each cell of the table as a Document and store and keep metadata (primary key, column name, table name, etc.) as stored,

Limiting a unqiue field search.

2004-07-19 Thread Shawn Konopinsky
I am attempting to query a field in my index for all unique values. I am using the following call to get all the unique values of the field: TermEnum enumerator = reader.terms(new Term(field, )); where read is an IndexReader and 'field' is the field name. However, I would like further limit

Misbehaving query string

2004-07-19 Thread Bill Tschumy
I would think the following strings passed to the QueryParser should yield the same results: #1: +telescope AND !operate #2: (+telescope) AND (!operate) However the first string seems to give the correct results while the second gives zero hits. Am I misunderstanding something or is there

Post-sorted inverted index?

2004-07-19 Thread Aphinyanaphongs, Yindalon
I gather from reading the documentation that the scores for each document hit are computed at query time. I have an application that, due to the complexity of the function, cannot compute scores at query time. Would it be possible for me to store the documents in pre-sorted order in the