That is neither the smallest possible code to show the problem, nor
self-contained. My guess would be that "reader" in your offending
line is the culprit. It isn't shown anywhere else in your code so,
from the evidence you've provided, it is reasonable to think it might
be null.
> hits[i].doc re
Hi,
here is the full part of the code:
public static void doPagingSearch(BufferedReader in, Searcher searcher,
Query query,
int hitsPerPage, boolean raw, boolean
interactive) throws IOException, ParseException,
InvalidTokenOffsetsException {
OK, so you've ruled out one possible cause. Progress!
But if you're getting NPE on line 274 and line 274 reads
TermPositionVector tpv =
(TermPositionVector)reader.getTermFreqVector(hits[i].doc,"contents");
then something is null where it shouldn't be. Rule out everything you
can and what is le
Hi,
no hits are not null, I can print all retrieved docuemtns without problem.
--
View this message in context:
http://lucene.472066.n3.nabble.com/highlighter-by-using-term-offsets-tp3527712p3533380.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
---
Thank you Mike,
I have thought about that solution myself, but the problem with this
approach is that the terms still need to be modified before building the
dictionary that is feed to the spell checker.
Also, the similarity scores which are used to determine the spell
suggestions are affected
Hello,
I'm having an issue with using NRT and Tax. After a couple of days of
running continuously , the taxonomyreader doesn't return results anymore
(but taxindex has them). How can i debug this?! does taxonomy index have a
logoutput like indexwriter has? will that be enough or relevant?
Current
