Here I am going further from my area of expertise so please buyer beware. The basic indexing options provide for a limited set of indexing types. Beyond that there are a lot of options to extend these to things like wildcard matches, range indexes (must be type aware to do that) some provide more capability in searching and others are performance tradeoffs (load time vs execution time, space vs time etc). But the default minimum case is that all element values and attribute values get at least an exact match index without having to do anything special. It does take a while to read up and experiment on these options to learn the details.
----------------------------------------------------------------------------- David Lee Lead Engineer MarkLogic Corporation [email protected] Phone: +1 650-287-2531 Cell: +1 812-630-7622 www.marklogic.com<http://www.marklogic.com/> This e-mail and any accompanying attachments are confidential. The information is intended solely for the use of the individual to whom it is addressed. Any review, disclosure, copying, distribution, or use of this e-mail communication by others is strictly prohibited. If you are not the intended recipient, please notify us immediately by returning this message to the sender and delete all copies. Thank you for your cooperation. From: [email protected] [mailto:[email protected]] On Behalf Of Todd Gochenour Sent: Tuesday, February 21, 2012 10:52 AM To: MarkLogic Developer Discussion Subject: Re: [MarkLogic Dev General] Processing Large Documents? Great. Good to hear that the database elements and attributes are indexed by default. eXistDB by default does the same. I'm looking at the Information Studio/Application Services/Database Settings page and wondering then what these options provide in addition to the default index.
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
