Confirm
574
edits
Changes
no edit summary
* Line-based searching without icky hacks ([https://github.com/elasticsearch/elasticsearch/issues/3022 nested queries are being a pain in the neck], but parent-child ones seem like a workable solution.)
* Caching of intermediate filter results. (It will transparently store the set of, say, all *.cpp files as a bitmap for quick set operations later. This means that common compound queries will likely be much faster than in any RDBMS.)
* Suggesters for "did you mean" and autocomplete
* Sparse attribute storage, which could come in handy for supporting new languages
* Extreme flexibility of indexing: index whatever chars we want, index them any number of ways (case-sensitive or not), and entirely too much more
Nice to have:
* Parallelization of even single queries
* Redundancy
* Scoring
=== Challenge: Fast Regex Matching ===
