[
https://issues.apache.org/jira/browse/SOLR-13402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16818815#comment-16818815
]
Uwe Schindler commented on SOLR-13402:
--------------------------------------
FYI, the order of clauses never has any effect on the underlying Lucene engine.
So I think in your queries there is something else wrong, I see "join" so this
is where I would look at.
> json dsl: order of must and must_not in serialization does matter?
> ------------------------------------------------------------------
>
> Key: SOLR-13402
> URL: https://issues.apache.org/jira/browse/SOLR-13402
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 8.0
> Reporter: Jochen Barth
> Priority: Major
> Attachments: solr-query1, solr-query2
>
>
> I have one(1) data structure representing a json dsl query, but depending on
> the serialization ({{must_not}} before/after {{must}} within
> {code:JSON}
> {"query":{"bool":{ ... }}}
> {code}
> ) this does return errnously 0 as numFound.
> * [^solr-query1] does return the correct number of hits
> * [^solr-query2] does return 0.
> Has the serialization to be "canonical" (keys of hashes sorted?)
> Thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
