RavenDB - Indexes Deep Dive
•
3 likes•2,475 views
This document provides an overview of indexes in RavenDB. It discusses how queries are processed, including the role of the Lucene index. It describes different types of indexes like temporary dynamic indexes, permanent dynamic indexes, and static indexes. The benefits of static indexes are outlined. Examples are provided of defining a simple static index and using indexing options like sorting, boosting, and live projections. The document also addresses how indexes can become stale and techniques for checking index staleness. Contact information is listed for additional RavenDB resources.
More Related Content
What's hot
What's hot (20)
Similar to RavenDB - Indexes Deep Dive
Similar to RavenDB - Indexes Deep Dive (20)
Recently uploaded
Recently uploaded (20)
RavenDB - Indexes Deep Dive
- 1. RavenDB A Deep Dive into Indexes S
- 2. Alonso Robles S Principal Consultant @ Headspring S Blog: http://alonsorobles.com S Linked In: http://linkedin.com/in/alonsorobles S Twitter: @alonsorobles
- 3. Central Texas GiveCamp September 28-30, 2012 Interested in Participating? Developer – Make software. Have fun. Do good! Non-Profit – What can we build for you? Sponsor – Help make the even successful. More Info: http://ctxgivecamp.org
- 4. The Query How does RavenDB find what we are looking for? S
- 5. Simple Query
- 6. What Happens? .NET Client sends query Server returns Server results processes query
- 7. How is the Query Processed?
- 8. The Index A short and brief introduction S
- 9. ACID versus BASE ACID BASE S Atomic S Basically Available S Consistent S Soft state S Isolated S Eventually consistent S Durable
- 10. ACID Document Operations S Store S Delete S Update
- 11. BASE Queries S Fast S Stale Results S Powered by Lucene
- 12. Lucene S Mature, De Facto Standard Information Retrieval Library S Scalable, High Performance Indexing S Powerful, Accurate and Efficient Search Algorithms S Originally Written in Java and Ported to Many Languages S Used by Apple, IBM, Linked In and many more…
- 13. Types of Indexes S Temporary Dynamic Index S Created on the fly to service a query when no existing index can be used S Permanent Dynamic Index S Promoted when a temporary index is used a lot S Static Index S User defined
- 14. Static Indexes Why? Aren’t the dynamic indexes enough? S
- 15. Reasons for Static Indexes S Index Creation is Expensive S Additional Functionality S Custom Sorting S Boosting S Full-Text Search S Live Projections S Spatial Search
- 17. Using the Index in a Query
- 18. Reducing Results
- 21. Live Projections
- 22. Stale Indexes Working with staleness S
- 23. Why Must It Be Stale? S Indexing occurs on a background thread S Keeps queries lightning fast S Better to be stale than offline
- 24. Checking for Stale Results
- 25. But Non-Stale Won’t Do
- 26. Questions Ask away! S
- 27. More Info S Official Raven Website: http://ravendb.net S Oren’s Blog: http://ayende.com S Google Group: http://groups.google.com/group/ravendb/ S My Blog: http://alonsorobles.com S Local Training: http://headspring.com
Editor's Notes
- Every index is required to have a name and a Map function. The Map function is the way for us to tell RavenDB how to find the data we are interested in, and what fields we are going to be searching on. The Map function is written in LINQ, just like you'd write a simple query
- The Reduce function is optional, and is written and executed just like the Map function, but this time on the results of the Map function. This is actually a second indexing pass, which allows us to perform aggregation operations quite cheaply, directly from the index.
- Sorting by default is performed lexographically.
- FieldStorageNo (default) – Does not store the value of the field in the indexYes – Stores the value of field Compress – Compresses the value of the field (good for long text or binary fields)FieldInexing OptionsAnalyzed – Standard analysis good for full text search or text fields (breaks up text into terms and performs stemming analysis)Default – LowerCaseKeywordAnalyzer (stores the entire field as a single term for exact matching)No – Field is not indexed thus cannot be searched. But it can still be accessed assuming it was stored.NotAnalyzed – Indexes the field without performing analysis. This is good for unique ids like product numbers (UPC, ISBN, MPN)
- Using the Live Projections feature, you have more control over what to load into the result entity, and since it returns a projection of the original entity, you also get the chance to filter out properties you do not need.
- WaitForNonStaleResultsAsOf()WaitForNonStaleResultsAsOfNow()WaitForNonStaleResultsAsOffLastWrite()