cross-field AND queries with field boosting

Hi, We have documents with multiple fields conceptually, and a document is considered a match if each of the terms in the query is in any one of the fields(i.e a 'cross-field' AND). A simple way to do this would be to dump all of these conceptual fields into one lucene field and do the query w

RE: Re: Where to download package org.apache.lucene.search.trie

Hi, You can use the artifact from Hudson as Mike told, but the JAR file is not compatible with Lucene 2.4 (because a new SortField constructor for sorting against trie encoded fields and the new Superinterface FieldCache.Parser leading to ClassNotFoundEx). If you want to use TrieRangeQuery/Filter,

Re: why would a Field *vanish* from a Document?

rolaren...@earthlink.net wrote: Now I notice (from googling) that I can also downcast TermFreqVector to TermPositionVector, which contains the offsets (which I will need). So -- under what conditions would that cast fail? The cast fails if you had indexed the field with Field.TermVect

Re: why would a Field *vanish* from a Document?

>> Now I notice (from googling) that I can also downcast TermFreqVector >> to TermPositionVector, which contains the offsets (which I will need). >> >> So -- under what conditions would that cast fail? > >The cast fails if you had indexed the field with Field.TermVector.YES, >which does not st

Re: problem in running lucene

http://lucene.apache.org/java/docs/ Apache Lucene is a high-performance, full-featured text search engine ***library*** written entirely in Java. Lucene is a search engine library not an application. You cannot execute it, you have to write your own code using the Lucene library to index or to

Re: problem in running lucene

Hello Sir, i downloaded lucene, then i went into the directory of jar file lucene-core-2.4.0.jar . I typed the command java -jar lucene-core-2.4.0.jar to run the jar file from command prompt. then the following error came "failed to load main-class manifest attribute from lucene-core-2.4.0.jar" . I

Re: why would a Field *vanish* from a Document?

rolaren...@earthlink.net wrote: Hey Mike -- Thanks for prompt & clear reply! This (the sneaky "difference" between an indexed Document and a the newly-created-at-search-time Document) is a frequent confusion with Lucene. The field needs to be marked as stored (Field.Store.YES) in order for

Re: IndexReader.isDeleted

OK, interesting, thanks. What do you use the deletedDocs iterator for? Yes, MatchAllDocsQuery should soon be fixed to not use the synchronized IndexReader.isDeleted method internally: https://issues.apache.org/jira/browse/LUCENE-1316 Mike John Wang wrote: Mike: "We are conside

Re: problem in running lucene

_