lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Barth (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SOLR-13402) json dsl: order of must and must_not in serialization does matter?
Date Tue, 16 Apr 2019 09:10:00 GMT

     [ https://issues.apache.org/jira/browse/SOLR-13402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jochen Barth resolved SOLR-13402.
---------------------------------
    Resolution: Not A Bug

Sorry, I am not able to reproduce this using the attached queries.


> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message