Hi Luceners..
Apologies...
Does this mean MultiFieldQueryParser will always have to use
'DEFAULT_OPERATOR_OR' instead of DEFAULT_OPERATOR_AND
operations.
Is there any alternative in handling this processs ( other then API
'replaceAll(" ", " AND ")' substution)
Please enlighten me
On Aug 17, 2005, at 1:50 PM, Karl Koch wrote:
Hello experts,
I have the following code:
Query query = QueryParser.parse(queryString, searchFields[0],
analyser);
Hits hits = searcher.search(query);
and the following code for search across multiple fields:
Query query = MultiFieldQueryP
On Aug 17, 2005, at 2:45 AM, Karthik N S wrote:
Hi Lucener's
Apologies..
I have seen forms using 'DEFAULT_OPERATOR_AND' with something
like below
> QueryParser parser = new QueryParser( "terms", analyzer);
> parser.setOperator(QueryParser.DEFAULT_OPERATOR_AND);
> query = par
On Aug 17, 2005, at 3:29 PM, Dan Funk wrote:
Currently I'm working with a single index where content is indexed
by it's original printed page. I have to show the total number of
matching documents, so I end up running through all the hits and
taking an order of magnitude hit on performance a
On Aug 17, 2005, at 2:49 PM, Karl Koch wrote:
Are there any other books (despite "Lucene in Action") perhaps
written in a
different perspective (e.g. different applications or problem areas)?
To echo what Otis said - I don't know of any myself.
I'd be very interested to hear yours, and other
On Wednesday 17 August 2005 22:49, Paul Elschot wrote:
> > the index could potentially be huge.
> >
> > So if this is indeed the case, it is a potential scalability
> > bottleneck in lucene index size.
>
> Splitting the date field into century, year in century, month, day, hour,
> seconds, and
>
On Wednesday 17 August 2005 22:36, Tony Schwartz wrote:
> Has anyone done any work on getting these types of terms or all terms for
> that matter
> into a collection that spilled onto the disk if necessary to avoid this
> problem? I'm
> just wondering if anyone has had any luck without crippling
Has anyone done any work on getting these types of terms or all terms for that
matter
into a collection that spilled onto the disk if necessary to avoid this
problem? I'm
just wondering if anyone has had any luck without crippling the search speed.
This is
definitely a problem that has burned
I don't know of any.
A search for "lucene" on Amazon.com will find a few other books, but as
far as I know, those books cover Lucene only briefly, in passing.
Otis
--- Karl Koch <[EMAIL PROTECTED]> wrote:
> Are there any other books (despite "Lucene in Action") perhaps
> written in a
> differen
Currently I'm working with a single index where content is indexed by
it's original printed page. I have to show the total number of matching
documents, so I end up running through all the hits and taking an order
of magnitude hit on performance as I calculate the number of unique
documents. I
Are there any other books (despite "Lucene in Action") perhaps written in a
different perspective (e.g. different applications or problem areas)?
Karl
--
5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail
+++ GMX - die erste Adresse für Mail, Message, More +++
---
Hello all,
I am developing code for Lucene 1.2 on a Sharp Zaurus using Java 1.1/1.2.
(Unfortunately I was not able to run version 1.3 on this setting.) Does
somebody know projects (eventually Open Source) also concerned with running
Lucene on platforms that only allow small footprint applications.
Hi All,
I have indexed a document collection using the option “WITH_POSITIONS”:
doc.add(new Field("contents", new FileReader(f),
Field.TermVector.WITH_POSITIONS));
...to get the positions in which each of the terms is found:
wordPositionsVector = termPositionVector.getTermPositions(wordIndex) ;
Hello Lucene experts,
I would like to insert my own scoring algorithm in Lucene 1.2 (I need to use
this old Lucene version due to hardware limitations (PDA and Java 1.2)). Has
somebody done things like that (eventually in the past) and can suggest
approaches and perhaps a code example? Workarounds
Hello experts,
I have the following code:
Query query = QueryParser.parse(queryString, searchFields[0], analyser);
Hits hits = searcher.search(query);
and the following code for search across multiple fields:
Query query = MultiFieldQueryParser.parse(queryString, searchFields,
analyser);
hits =
Hello experts,
I have the following code:
Query query = QueryParser.parse(queryString, searchFields[0], analyser);
Hits hits = searcher.search(query);
and the following code for search across multiple fields:
Query query = MultiFieldQueryParser.parse(queryString, searchFields,
analyser);
hits =
Hi
Lucener's
Apologies..
I have seen
forms using 'DEFAULT_OPERATOR_AND' with
something like below >
QueryParser parser = new QueryParser( "terms", analyzer); >
parser.setOperator(QueryParser.DEFAULT_OPERATOR_AND); > query =
parser.parse(TextParameters);
How to use
the DEFA
17 matches
Mail list logo
