Actually, I think I know the issue. My Solr tests were subject to caching, and
while they were all intended to be different I think the .equals and .hashCode
are broken on SpanPayloadCheckQuery. In my stumbling around, I had also made
this change which I now suspect is the fix I needed:
$ gi
Alan,
Thanks again for the quick replies and assistance. As these things go, I did a
clean build and my query parser started working properly. Actually I wrote
some tests to test out the situation I reported and my tests confirmed how I
thought it should have worked and that got me to do a cl
Hm, maybe - a quick look at the tests suggests that we don’t have anything that
explicitly checks more than 2 clauses. Can you open an issue and add something
to TestPayloadCheckQuery?
> On 25 Apr 2017, at 10:23, Erik Hatcher wrote:
>
> Alan - thanks for the reply. Given your explanation is
Alan - thanks for the reply. Given your explanation is there an off by one
term issue? The matches I'm seeing would happen if the last term weren't
considered.
Do you have an example of multiple payloads too?
Erik
> On Apr 25, 2017, at 04:16, Alan Woodward wrote:
>
> The query will o
The query will only match a particular span if all the payloads in that span
match the passed-in array. So for example, in your first query, the inner
spanNear query matches two terms (words_dps:one and words_dps:two), so it needs
to have an array of two payloads to match.
You can use it for,
I’ve started a belated mission to leverage payloads from Solr (SOLR-1485),
mainly from float payload decoding for weighting in scoring, but while digging
in I’m exploring all that payloads now have to offer including the
SpanPayloadCheckQuery. However, I’m not yet understanding how to use it
