For posterity, in case anybody follows this thread, I tracked the
problem down to WordDelimiterFilter; apparently it creates an offset of
-1 in some case, which PostingsHighlighter rejects.
-Mike
On 5/2/2014 10:20 AM, Michael Sokolov wrote:
I checked using the analysis admin page, and I
Hello michael, you are not on lucene 4.8?
https://issues.apache.org/jira/plugins/servlet/mobile#issue/LUCENE-5111
Michael Sokolov msoko...@safaribooksonline.com schreef:For posterity, in case
anybody follows this thread, I tracked the
problem down to WordDelimiterFilter; apparently it creates
Hi,
so this is all about posIncAttribute?
I had opened https://issues.apache.org/jira/browse/SOLR-3193, about
ReversedWildcardFilterFactory is causing highlighter exceptions. I wonder
ReversedWildcardFilter has similar bug.
Ahmet
On Saturday, May 3, 2014 9:39 PM, Markus Jelsma
No not yet; but that could be one more reason to upgrade. The
performance boost from PH is quite nice. In my test, it's about 7x
faster than the default highlighter, almost 2x faster than fast vector
highlighter, and only about a 50% penalty compared to no highlighting at
all, so this could
I've been wanting to try out the PostingsHighlighter, so I added
storeOffsetsWithPositions to my field definition, enabled the
highlighter in solrconfig.xml, reindexed and tried it out. When I
issue a query I'm getting this error:
|field 'text' was indexed without offsets, cannot highlight
I checked using the analysis admin page, and I believe there are offsets
being generated (I assume start/end=offsets). So IDK I am going to try
reindexing again. Maybe I neglected to reload the config before I
indexed last time.
-Mike
On 05/02/2014 09:34 AM, Michael Sokolov wrote:
I've
