Re: default AND operator

: Why does my query "french AND antiques" work the way I expect using this : code: can you be more specific about what it is you "expect", and what exactly serachTerms is in your examples? (presumably it's a string, is it the string "french AND antiques" ... are you sure it's not "french and ant

Re: Example question

: No, I am talking about the Lucene Examples (not from LIA). you're going to need to be more specific about what you mean ... what is the exact location of the file where you are seeing the "Example" in question? ... is it a URL? is it a file from a release you downloaded? what is the URL of the

default AND operator

Why does my query "french AND antiques" work the way I expect using this code: stemParser = new QueryParser("contents", stemmingAnalyzer); Query query = stemParser.parse(searchTerms); Hits docHits = searcher.search(query); Debug from query shows: contents:french contents:antiqu ... I would h

Re: Example question

No, I am talking about the Lucene Examples (not from LIA). On 9/16/06, Erik Hatcher <[EMAIL PROTECTED]> wrote: Are you talking about the LIA example code? The sample data gets indexed using the Ant task, which automatically adds a "path" field for every document. You'll see the document h

Re: Example question

Are you talking about the LIA example code? The sample data gets indexed using the Ant task, which automatically adds a "path" field for every document. You'll see the document handler mentioned in the LIA build.xml file as well as the code for it in the code download. Erik

RE: Merging "orphaned" segments into a composite index

Thanks for the advice, Andrzej, including using BeanShell for this. SegmentInfos and CompoundFileReader here I come. -Original Message- From: Andrzej Bialecki [mailto:[EMAIL PROTECTED] Sent: 16 September 2006 14:09 To: java-user@lucene.apache.org Subject: Re: Merging "orphaned" segments i

Better Highligther fragmenter?

I'm now using the excellent Hightlighter from within Solr and it works very well; except that the generated fragments sometimes begins with bad-looking characters (the "." of the end of the previous phrase, or a ), /10, etc). The same is true for the fragments ends. I looked at both the dev and

Re: Real world app advice

Of course, the answer is "it depends" . This doesn't sound like a very big index, so the first approach I'd make is making the index complicated and keeping the queries as simple as possible. This assumes that you really don't care about indexing speed/size and response time for searches is wh

Example question

While looking at the example's Index and Search code, I have noticed in the search, there is a : out.println (doc.get ("path")); I am not sure how is "path" is getting into the index. If you take a look at the Index code, there is no mention of "path". My question are: what is this path (I know

RE: best way to get specific results

: IndexSearcher.search(Query, Filter) method). Im just wrapping a : ConstantScoreQuery around the filter, and passing it into the : IndexSearcher.search(Query) method to return a Hits object. Then Im : asking for the 500th to 550th doc in the Hits object. : : Would such a case still cause Hits to r

Re: Merging "orphaned" segments into a composite index

Rob Staveley (Tom) wrote: It looks like my segments file only contains information for the .cfs segments. So this approach doesn't work. I was wondering if I could use IndexWriter.addIndexes(IndexReader[]) instead. Can I open an IndexReader without a corresponding segments file? In notice that In

RE: Merging "orphaned" segments into a composite index

It looks like my segments file only contains information for the .cfs segments. So this approach doesn't work. I was wondering if I could use IndexWriter.addIndexes(IndexReader[]) instead. Can I open an IndexReader without a corresponding segments file? In notice that IndexReader.open(...) always o