> Am I right that the MemoryIndex with getReader() is
> not available
> anywhere at this point?
createReader() is the method you need. I think the
latest SVN version has it.
___
To help you stay safe and secure online,
Thanks Mark for your pointers. I'm deep into this, trying to wire
something up.
Am I right that the MemoryIndex with getReader() is not available
anywhere at this point?
Thanks,
Fred
At 11:53 AM 8/25/2005, mark harwood wrote:
>> but I'm still lost on how to convert
> everything to SpanQuery
>
On Aug 24, 2005, at 7:47 PM, Fred Toth wrote:
However, after reviewing recent discussions about highlighting,
and struggling with our own highlighting issues, I'm wondering if
there's a better way.
Here's one way. This is the algo used by a developer's version of my
Perl/C search engine libr
>> but I'm still lost on how to convert
> everything to SpanQuery
> variants.
See the QuerySpansExtractor I linked to here:
http://issues.apache.org/bugzilla/show_bug.cgi?id=35518
This uses SpanTermQuery for individual TermQuerys. As
for all of the other query types eg fuzzy, prefix,
range etc th
Based on this discussion, I've gone back and re-read everything
in LIA on SpanQuery, etc.
Isn't this just another manifestation of the same problem? How
do I reliably, correctly convert an arbitrary lucene query into its
equivalent SpanQuery?
Here's one, for example:
+text:"jurassic barnea" +au
Unfortunately I've not had the time to address the
phrase highlighting issues in the current highlighter
but I think I've an idea as to how best to fix it:
I would suggest rewriting the highlighter to use Spans
not Terms to find the relevant sections in a text.
Most of the code required for such a
Hi,
on our setup, we are using two completely separated processes, one to
search and another to highlight the found documents. Both this
processes are used by other applications through xml-rpc calls.
Our index is used to search the content of an Oracle DB; for this
reason, there are no stored fi
On Thursday 25 August 2005 04:47, Fred Toth wrote:
> All,
>
> First, my thanks to those who've contributed to the current
> best practices for highlighting. We use your code!
>
> However, after reviewing recent discussions about highlighting,
> and struggling with our own highlighting issues, I'm
All,
First, my thanks to those who've contributed to the current
best practices for highlighting. We use your code!
However, after reviewing recent discussions about highlighting,
and struggling with our own highlighting issues, I'm wondering if
there's a better way.
Others have certainly thoug
