From 34f2c74331991a1cc1bf3083ced511632fdf141d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Xavier=20L=C3=A9aut=C3=A9?= <xavier@metamarkets.com>
Date: Tue, 21 Oct 2014 17:24:44 -0700
Subject: [PATCH] add docs

---
 docs/content/Aggregations.md | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/docs/content/Aggregations.md b/docs/content/Aggregations.md
index abd4780b025..1ff60721c39 100644
--- a/docs/content/Aggregations.md
+++ b/docs/content/Aggregations.md
@@ -160,3 +160,28 @@ Uses [HyperLogLog](http://algo.inria.fr/flajolet/Publications/FlFuGaMe07.pdf) to
 ```json
 { "type" : "hyperUnique", "name" : <output_name>, "fieldName" : <metric_name> }
 ```
+
+## Miscellaneous Aggregations
+
+### Filtered Aggregator
+
+A filtered aggregator wraps any given aggregator, but only aggregates the values for which the given dimension filter matches.
+
+This makes it possible to compute the results of a filtered and an unfiltered aggregation simultaneously, without having to issue multiple queries, and use both results as part of post-aggregations.
+
+*Limitations:* The filtered aggregator currently only supports selector filters, i.e. matching a dimension against a single value.
+
+*Note:* If only the filtered results are required, consider putting the filter on the query itself, which will be much faster since it does not require scanning all the data.
+
+```json
+{
+  "type" : "filtered",
+  "name" : "aggMatching",
+  "filter" : {
+    "type" : "selector",
+    "dimension" : <dimension>,
+    "value" : <dimension value>
+  }
+  "aggregator" : <aggregation>
+}
+```