That is spooky. It certainly sounds like a regression.
It's odd that your MultiTermEnum is pulling an AllTermDocs under the
hood -- this should only happen if you did a .seek(null) on it, but
your code seems to first check that term != null, so it should never
pass a null term.
Can you add a tem
This idea has been discussed a few times on the list... eg try
googling on "incremental document field update".
It's tricky; Lucene doesn't make it easy to update just a portion of a
document's postings information. The implementation will be very
different from updateDocument...
Mike
On Tue, J
I opened LUCENE-2526 for this...
Mike
On Thu, Jul 1, 2010 at 2:19 PM, Woolf, Ross wrote:
> In Lucene 2.9.2 (have not checked 3.x) calling MultiPhraseQuery.toString()
> throws a null pointer exception. Below is very simple code to test this out.
>
> import org.apache.lucene.search.MultiPhraseQu
Hmm it looks like we should move UnionDocsAndPositionsEnum out of
MultiPhraseQuery, into oal.index, and make it public (like
MultipleTermPositions is in 3.x). And note this in MIGRATE.txt.
I'll open an issue...
Mike
On Sun, Jun 27, 2010 at 9:13 PM, Robert Muir wrote:
> On Sun, Jun 27, 2010 at
