Am 23.04.2013 16:17, schrieb Alan Woodward:
> It doesn't sound as though an inverted index is really what you want to be
> querying here, if I'm reading you right. You want to get the payloads for
> spans at a specific position, but you don't particularly care about the
> actual term at that p
Hi Carsten,
It doesn't sound as though an inverted index is really what you want to be
querying here, if I'm reading you right. You want to get the payloads for
spans at a specific position, but you don't particularly care about the actual
term at that position? You might find that BinaryDocV
Am 23.04.2013 15:27, schrieb Alan Woodward:
> There's the SpanPositionCheckQuery family - SpanRangeQuery, SpanFirstQuery,
> etc. Is that the sort of thing you're looking for?
Hi Alan,
thanks for the pointer, this is the right direction indeed. However,
these queries are based on a SpanQuery whic
There's the SpanPositionCheckQuery family - SpanRangeQuery, SpanFirstQuery,
etc. Is that the sort of thing you're looking for?
Alan Woodward
www.flax.co.uk
On 23 Apr 2013, at 13:36, Carsten Schnober wrote:
> Am 23.04.2013 13:47, schrieb Carsten Schnober:
>> I'm trying to figure out a way to u
Am 23.04.2013 13:47, schrieb Carsten Schnober:
> I'm trying to figure out a way to use a query as Uwe suggested. My
> scenario is to perform a query and then retrieve some of the payloads
> upon user request, so there no obvious way to wrap this into a query as
> I can't know what (terms) to query
Am 23.04.2013 13:21, schrieb Michael McCandless:
> Actually, term vectors can store payloads now (LUCENE-1888), so if that
> field was indexed with FieldType.setStoreTermVectorPayloads they should be
> there.
>
> But I suspect the TokenSources.getTokenStream API (which I think un-inverts
> the ter
Actually, term vectors can store payloads now (LUCENE-1888), so if that
field was indexed with FieldType.setStoreTermVectorPayloads they should be
there.
But I suspect the TokenSources.getTokenStream API (which I think un-inverts
the term vectors to recreate the token stream = very slow?) wasn't f
TermVectors are per-document and do not contain payloads. You are reading the
per-document TermVectors which is a "small index" *stored* for each document as
a binary blob. This blob only contains the terms of this document with its
positions/offsets, but no payloads (offsets are used e.g. for h