search:and-not-query is ignored in QueryBatcher about java-client-api

[rjrudin]

Thanks @marcopacurariu3 , we'll work on reproducing this today and will report back to you.

[marcopacurariu3]

Great @rjrudin, thank you!

[rjrudin]

@marcopacurariu3 I haven't had luck reproducing this yet. I added a new JUnit test - acb5085#diff-52e216474c59fcf9a974f2706e674b08ef0c484eee84fb74a7839b0439c99bd5R186 - that does the following:

1. Adds the same XML doc with different URIs to collections test1 and test2.
2. Verifies that a regular structured and-not query (with a term-query on "world", which is in both documents) works.
3. Verifies that a combined and-not-query works.
4. Verifies that the same combined and-not-query works with DMSDK.

I also verified that if I comment out the and-not query, then the test fails as it returns 2 documents instead of only 1.

So the and-not-query appears to be getting picked up in all cases.

Could you try modifying your query to do a term-query instead of a range-constraint-query? Looks like you could just do a term-query on "testapp". Perhaps the issue requires the use of both a range query and a set of search options.

[marcopacurariu3]

Sure, I will play around and come back to you tomorrow.

Thanks a lot for digging into it.

[marcopacurariu3]

@rjrudin, thanks once again for the implemented test. This helped me finding out the real issue. It works with range-constraing-query in your example, too, so it's not that.

The issue is that I am using "positive/negative" instead of "positive**-query**/negative**-query**".

So, "positive" works in a simple search, but it does not work in QueryBatcher. The QueryBatcher supports only "positive-query" or "negative-query".

Here is the query that for me it works in search, but not in batcher:

"<search xmlns=\"http://marklogic.com/appservices/search\">\n" +
                    "  <query>\n" +
                    "    <and-query>\n" +
                    "      <range-constraint-query>\n" +
                    " <constraint-name>application</constraint-name>\n" +
                    " <value>testapp</value>\n" +
                    "<range-operator>EQ</range-operator>\n" +
                    " </range-constraint-query>\n" +
                    "      <and-not-query>\n" +
                    "        <positive>\n" +
                    "          <collection-query>\n" +
                    "            <uri>test1</uri>\n" +
                    "          </collection-query>\n" +
                    "        </positive>\n" +
                    "        <negative>\n" +
                    "          <collection-query>\n" +
                    "            <uri>test2</uri>\n" +
                    "          </collection-query>\n" +
                    "        </negative>\n" +
                    "      </and-not-query>\n" +
                    "    </and-query>\n" +
                    "  </query>\n" +
                    "</search>"

I assume that if you do the same in your test, then you will notice the issue.

[rjrudin]

Hi @marcopacurariu3 - I checked the docs for a structured and-not-query - https://docs.marklogic.com/guide/search-dev/structured-query#id_65108 - and it does require positive-query and negative-query. I'm a little surprised the server doesn't reject positive and negative but rather ignores it.

I'm not sure why your query would work with positive and negative as I'm fairly certain those should always be ignored. I verified in my test that if I use those element names, the test fails.

I think the right approach here is to use positive-query and negative-query per the server docs link above. I'm going to close this, but please let me know if you run into issues with those elements working.