Now in master, and will be part of 0.9 is much more enhanced facets
support. On top of the query facet that came with elasticsearch previous
versions, there are now:
On top of that, all facets can now accept filters that filter even more the
"result set" they operate on. Also, there are new and, or, and not
filters that are faster than the bool filter, see more here:
The global flag is applicable as well to all facets, controlling if they
will be bounded by the executing query, or run globally (and bounded by the
filters).
When you have time, take it for a spin and tell me what you think. Other
facets should be simple to implement (they must be "map reduce-able"), so if
you have an idea for one, just shout.
Now in master, and will be part of 0.9 is much more enhanced facets
support. On top of the query facet that came with elasticsearch previous
versions, there are now:
The global flag is applicable as well to all facets, controlling if they
will be bounded by the executing query, or run globally (and bounded by the
filters).
When you have time, take it for a spin and tell me what you think. Other
facets should be simple to implement (they must be "map reduce-able"), so if
you have an idea for one, just shout.
Very nice - out of interest, why do Lucene use should|must|mustNot
rather than the more obvious (to me, at least) and|or|not, especially if
(as you say) the latter performs better?
Its just an extension to filters that provide that called bool filter, and I
guess the idea was to create something similar to the boolean query. The
other ones (and/or/not) are not part of Lucene or its modules.
Very nice - out of interest, why do Lucene use should|must|mustNot
rather than the more obvious (to me, at least) and|or|not, especially if
(as you say) the latter performs better?
Its just an extension to filters that provide that called bool filter, and
I guess the idea was to create something similar to the boolean query. The
other ones (and/or/not) are not part of Lucene or its modules.
Very nice - out of interest, why do Lucene use should|must|mustNot
rather than the more obvious (to me, at least) and|or|not, especially if
(as you say) the latter performs better?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
