Hello, Thanks for all the replies. They are very helpful. Chunyu On 3 July 2015 at 20:00, <[email protected]> wrote:
> Send General mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://developer.marklogic.com/mailman/listinfo/general > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of General digest..." > > > Today's Topics: > > 1. Re: rang index for string element (Christopher Hamlin) > 2. Re: rang index for string element (Erik Hennum) > 3. Re: rang index for string element (Florent Georges) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 3 Jul 2015 09:36:43 -0400 > From: Christopher Hamlin <[email protected]> > Subject: Re: [MarkLogic Dev General] rang index for string element > To: MarkLogic Developer Discussion <[email protected]> > Message-ID: > <CADX+0QyUW=W2FEAFAfB_n=VOYH= > [email protected]> > Content-Type: text/plain; charset=UTF-8 > > Hi, > > If you want to search for an element containing a particular string > value, you can use cts:element-value-query, and this requires no extra > indexing. Element string values are also automatically indexed. > Inside MarkLogic Server is great for overall technical info like this: > https://developer.marklogic.com/inside-marklogic. > > You'd likely use a range index if you want to compare values (less > than, greater than), or return values (all string values for a certain > element), or return counts for values. > > And, as Raja says, a more specific question can get a more specific answer. > > =Chris > > On Fri, Jul 3, 2015 at 9:08 AM, Chunyu Cong <[email protected]> wrote: > > 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 > > [email protected] > > Manage your subscription at: > > http://developer.marklogic.com/mailman/listinfo/general > > > > > ------------------------------ > > Message: 2 > Date: Fri, 3 Jul 2015 13:43:14 +0000 > From: Erik Hennum <[email protected]> > Subject: Re: [MarkLogic Dev General] rang index for string element > To: MarkLogic Developer Discussion <[email protected]> > Message-ID: > < > dfdf2fd50bf5aa42adaf93ff2e3ca185070e9...@exchg10-be01.marklogic.com> > Content-Type: text/plain; charset="iso-8859-1" > > 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: [email protected] [ > [email protected]] on behalf of Chunyu Cong [ > [email protected]] > Sent: Friday, July 03, 2015 6:08 AM > To: [email protected] > 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 > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://developer.marklogic.com/pipermail/general/attachments/20150703/6c13da6d/attachment-0001.html > > ------------------------------ > > Message: 3 > Date: Fri, 3 Jul 2015 15:47:02 +0200 > From: Florent Georges <[email protected]> > Subject: Re: [MarkLogic Dev General] rang index for string element > To: MarkLogic Developer Discussion <[email protected]> > Message-ID: > < > cadyr_r2dfms8vf2veczmg7xzzkccdc9_ovnsydtgyderhmu...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hi, > > Very, very basically, the universal index will index words and > co-occurrence between 2 different words. Which let you search > efficiently (like searches you would do on Google, using phrases, > several words, different weights depending on the distance between the > words you search for, etc.) > > Range indexes index values. A string range index will then be > useful for enumerations or elements that you will typically search for > exact matches. Range indexes are ordered also, and let you order > results very efficiently. A very common use case for range indexes > are facets. > > If you describe what you want to achieve, we can tell you more. > > Regards, > > -- > Florent Georges > http://fgeorges.org/ > http://h2oconsulting.be/ > > > On 3 July 2015 at 15:08, Chunyu Cong wrote: > > 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 > > [email protected] > > Manage your subscription at: > > http://developer.marklogic.com/mailman/listinfo/general > > > > > ------------------------------ > > _______________________________________________ > General mailing list > [email protected] > Manage your subscription at: > http://developer.marklogic.com/mailman/listinfo/general > > > End of General Digest, Vol 133, Issue 11 > **************************************** >
_______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
