Hi, David: The collections should be OR related with one another. The list of collections as a whole should be AND related with the structured query.
If that's not what you're seeing, please file a bug with a reproduction case through Support so it can be tracked and prioritized appropriately. Erik Hennum ________________________________ From: general-boun...@developer.marklogic.com [general-boun...@developer.marklogic.com] on behalf of David Mathei [david.mat...@lambdawerk.com] Sent: Monday, July 10, 2017 6:39 AM To: MarkLogic Developer Discussion Subject: [MarkLogic Dev General] ML9 rest-api does not honor 'collection' parameter in search? Good afternoon, I observed that GETting /v1/search?collection=<coll>&structuredQuery=<q> does not filter the results to the collection-members in ML9. /v1/search?collection=<coll> does what I'd expect from it, and moving the collection constraint into structuredQuery also works as advertised. In ML8 the first version above also observes teh query and the collection filter. The two databases are constructed with teh same properties. Is there an explanation for this behaviour or is this a bug? I've tested this with a minimal example which I have attached below. Thanks, David
_______________________________________________ General mailing list General@developer.marklogic.com Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general