I guess this also ties in with 'getPositionIncrementGap', which is relevant
to fields with multiple occurrences.
Peter
On 7/27/07, Peter Keegan [EMAIL PROTECTED] wrote:
I have a question about the way fields are analyzed and inverted by the
index writer. Currently, if a field has multiple
I'm looking for Spans.getPositions(), as shown in BoostingTermQuery, but
neither NearSpansOrdered nor NearSpansUnordered (which are the Spans
provided by SpanNearQuery) provide this method and it's not clear to me how
to add it.
Peter
On 7/11/07, Chris Hostetter [EMAIL PROTECTED] wrote:
:
That is off of the TermSpans class. BTQ (BoostingTermQuery) is
implemented to extend SpanQuery, thus SpanNearQuery isn't, w/o
modification, going to have access to these things. However, if you
look at the SpanTermQuery, you will see that it's implementation of
Spans is indeed the
On Thursday 12 July 2007 14:50, Grant Ingersoll wrote:
That is off of the TermSpans class. BTQ (BoostingTermQuery) is
implemented to extend SpanQuery, thus SpanNearQuery isn't, w/o
modification, going to have access to these things. However, if you
look at the SpanTermQuery, you will
Yep, totally agree.One way to handle this initially at least is
have isPayloadAvailable() only return true for the SpanTermQuery.
The other option is to come up with some modification of the
suggested methods below to return all the payloads in a span.
I have a basic implementation
Grant,
If/when you have an implementation for SpanNearQuery, I'd be happy to test
it.
Peter
On 7/12/07, Grant Ingersoll [EMAIL PROTECTED] wrote:
Yep, totally agree.One way to handle this initially at least is
have isPayloadAvailable() only return true for the SpanTermQuery.
The other
: That is off of the TermSpans class. BTQ (BoostingTermQuery) is
...
: I am not completely sure here, but it seems like we may need an
: efficient way to access the TermPositions for each document. That
: is, the Spans class doesn't provide this and maybe it should
...
: I'm
On Jul 12, 2007, at 6:12 PM, Chris Hostetter wrote:
Hmm... okay so the issue is that in order to get the payload data, you
have to have a TermPositions instance.
instead of adding getPayload methods to the Spans class (which as Paul
points out, can have nesting issues) perhaps more general
I'm now looking at using payloads with SpanNearQuery but I don't see any
clear way of getting the payload(s) from the matching span terms. The term
positions for the payloads seem to be buried beneath SpanCells in the
NearSpansOrdered and NearSpansUnordered classes, which are not public. I'd
be
: I'm now looking at using payloads with SpanNearQuery but I don't see any
: clear way of getting the payload(s) from the matching span terms. The term
: positions for the payloads seem to be buried beneath SpanCells in the
Isn't Spans.start() and Spans.end() what you are looking for?
-Hoss
I tried to subclass PhraseScorer, but discovered that it's an abstract class
and its subclasses (ExactPhraseScorer and SloppyPhraseScorer) are final
classes. So instead, I extended Scorer with my custom scorer and extended
PhraseWeight (after making it public). My scorer's constructor is passed
I'm looking at the new Payload api and would like to use it in the following
manner. Meta-data is indexed as a special phrase (all terms at same
position) and a payload is stored with the first term of each phrase. I
would like to create a custom query class that extends PhraseQuery and uses
its
You cannot do it because TermPositions is read in the
PhraseWeight.scorer(IndexReader) method (or MultiPhraseWeight) and
loaded into an array which is passed to PhraseScorer. Extend the Weight
as well and pass the payload to the Scorer as well is a possibility.
- Mark
Peter Keegan wrote:
I'm
Could you get what you need combining the BoostingTermQuery with a
SpanNearQuery to produce a score? Just guessing here..
At some point, I would like to see more Query classes around the
payload stuff, so please submit patches/feedback if and when you get
a solution
On Jun 27, 2007, at
14 matches
Mail list logo
