Hi Tim, By default, cts:search() runs filtered queries and cts:uris() only runs unfiltered queries. Think of unfiltered queries as queries that are resolved based on index information alone. In other words, there isn't enough information in your indexes for cts:uris() to resolve accurately. If you chose to run cts:search() unfiltered, I expect you would see the same thing.
If you enable the "word position" and "element word position" indexes on your database, then I expect you would see the correct results from cts:uris() after the database finishes creating those indexes. Best, Rob Rob Szkutak Senior Consultant MarkLogic Corporation rob.szku...@marklogic.com Cell +1.716.562.8464 www.marklogic.com<http://www.marklogic.com> ________________________________ From: general-boun...@developer.marklogic.com [general-boun...@developer.marklogic.com] on behalf of Tim Meagher [t...@aaom.net] Sent: Thursday, September 08, 2016 12:28 PM To: 'MarkLogic Developer Discussion' Subject: [MarkLogic Dev General] Embedded element queries work in cts:search but not in cts:uris? Hi Folks, I have been able to successfully use embedded cts;element-value-query() calls within cts:element-query() under cts:search to emulate an xpath query, but using the same embedded call within cts:uris does not limit the results the context of the cts:element-query(). I’m using ML7.0-5. Is this a bug or a feature? Tim Meagher – Just some person trying to make a living…
_______________________________________________ General mailing list General@developer.marklogic.com Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
