From 9f93be448e41cac8913f2005b12324770079e780 Mon Sep 17 00:00:00 2001 From: Kirill Kozlov Date: Tue, 7 Jun 2016 19:44:18 +0200 Subject: [PATCH] Fix logical operator in example (#3093) --- docs/content/querying/multi-value-dimensions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/querying/multi-value-dimensions.md b/docs/content/querying/multi-value-dimensions.md index 626d8c8eb1a..1e8953c9d1a 100644 --- a/docs/content/querying/multi-value-dimensions.md +++ b/docs/content/querying/multi-value-dimensions.md @@ -88,7 +88,7 @@ This "selector" filter would match row4 of the dataset above: topN and groupBy queries can group on multi-value dimensions. When grouping on a multi-value dimension, _all_ values from matching rows will be used to generate one group per value. It's possible for a query to return more groups than -there are rows. For example, a topN on the dimension `tags` with filter `"t1" OR "t3"` would match only row1, and +there are rows. For example, a topN on the dimension `tags` with filter `"t1" AND "t3"` would match only row1, and generate a result with three groups: `t1`, `t2`, and `t3`. If you only need to include values that match your filter, you can use a [filtered dimensionSpec](dimensionspecs.html#filtered-dimensionspecs). This can also improve performance.