Hi Damon I am using this particular condition to exclude some of the fragments.
Path range index is not allowing me to use wildcard so I have to supply list of values instead of specifying a wildcard like *. Even my stats show when we supply more values it taking more time than expected or condition. I tried with using or query with each value in path index and it's working in much better way. So I believe the path range index with multiple values is not performing well compared to or condition. I believe for now it's good to use or condition with multi path range queries than passing multiple values to a path range query. Would love to hear thoughts on this. Regards, Gnana(GP) -------------- Message: 3 Date: Mon, 5 May 2014 17:35:26 +0000 From: Damon Feldman <[email protected]> Subject: Re: [MarkLogic Dev General] path range query taking more time when multiple values are supplied To: MarkLogic Developer Discussion <[email protected]> Message-ID: <2abb2109db4965418f09773e1b6006420557b...@exchg10-be02.marklogic.com> Content-Type: text/plain; charset="iso-8859-1" Ganaprakash, That first form is a 4-way OR so may be slightly more complex to build, though I don't see it on my machine. This line - the actual building of the constraint structure - is likely to have a minor performance impact compared to the actual query execution. Is there a reason you want to optimize this line? Yours, Damon From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Saturday, May 03, 2014 11:34 AM To: [email protected] Subject: [MarkLogic Dev General] path range query taking more time when multiple values are supplied Hi I am profiling one of my queries and found that path range query is taking more time when multiple values are passed. Example: cts:path-range-query("*:resource/*:level/*:level/*:level/@type","=",("module","lesson","unit","day") ,$case-insensitive-collation) Shallow ?s: 600-900 takes more time than cts:path-range-query("*:resource/*:level/*:level/*:level/@type","=","module",$case-insensitive-collation) Shallow ?s: 60-80 Is this expected behaviour? Is there any other alternative approach of using multiple values based path range query? Regards, Gnanaprakash Bodireddy This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
