Hi, Chunyu: You should create a string range index to do any of the following:
* document sort * value lookups with document or value frequency (ie, facets) * value projection in co-occurring tuples * lexical order comparison queries (as in somePropertyOrElement < "c") You can also use a string range index for exact matching (instead of stemmed matching) or to speed up queries on a frequently-queried JSON property or XML element or attribute. As with many things computational, there is a tradeoff -- in this case adding a little to the index time and to the memory requirements. Hoping that helps, Erik Hennum ________________________________ From: general-boun...@developer.marklogic.com [general-boun...@developer.marklogic.com] on behalf of Chunyu Cong [congchu...@gmail.com] Sent: Friday, July 03, 2015 6:08 AM To: General@developer.marklogic.com Subject: [MarkLogic Dev General] rang index for string element Hello, I understand Marklogic index words automatically. What happens if we add range index for the string element? Is that never needed? Or the range index could speed up searching on string? Thanks, Chunyu
_______________________________________________ General mailing list General@developer.marklogic.com Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
