Thanks for your help, great solution! Turned out perfectly. Too bad they
don't actually add this to the sdk.
--
View this message in context:
http://lucene.472066.n3.nabble.com/AndQueryNode-to-NearSpanQuery-tp3061286p3066035.html
Sent from the Solr - User mailing list archive at Nabble.com.
Thanks for the correction! I thought I had read that phrases were assumed to
be in order and the slop was the distance between them. I'll look into this
also.
--
View this message in context:
http://lucene.472066.n3.nabble.com/AndQueryNode-to-NearSpanQuery-tp3061286p3063673.html
Sent fro
That is a really good idea. I'll have to try that.
--
View this message in context:
http://lucene.472066.n3.nabble.com/AndQueryNode-to-NearSpanQuery-tp3061286p3063668.html
Sent from the Solr - User mailing list archive at Nabble.com.
slate all the children into
> SpanQueries and put them into a subsequent NearSpanQuery at the builder
> stage, but this is still pretty incompatible with most of the pipeline.
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/AndQueryNode-to-NearSpanQuery-tp3061286p3061607.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
t; Von: mtraynham
> An: solr-user@lucene.apache.org
> Betreff: AndQueryNode to NearSpanQuery
> ...
> The SpanNearQueryNode is a class I made that implements FieldableNode
> and extends QueryNodeImpl (as I want all Fieldable children to be from
> the same field, therefore just remember
ueries and put them into a subsequent NearSpanQuery at the builder
stage, but this is still pretty incompatible with most of the pipeline.
--
View this message in context:
http://lucene.472066.n3.nabble.com/AndQueryNode-to-NearSpanQuery-tp3061286p3061607.html
Sent from the Solr - User mailing li
I'd rather stay away from monkey patching.
>
> I thought about adding another array, "terms", that would maintain the
> original children array, but that also experiences quite a few
> inconveniences and conflicts with monkey patching.
>
> Any ideas? Any help would b
;, that would maintain the
original children array, but that also experiences quite a few
inconveniences and conflicts with monkey patching.
Any ideas? Any help would be much appreciated.
--
View this message in context:
http://lucene.472066.n3.nabble.com/AndQueryNode-to-NearSpanQuery-tp3061286
