From f62221bfae5e7aa6cf50dbe931b4e3c8cd1779c7 Mon Sep 17 00:00:00 2001 From: Igal Levy Date: Thu, 23 Oct 2014 14:30:02 -0700 Subject: [PATCH] added link to DimensionSpec for alternative way to provide dimensions --- docs/content/GroupByQuery.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/GroupByQuery.md b/docs/content/GroupByQuery.md index 0c6cf0cdf67..c010d8daf6c 100644 --- a/docs/content/GroupByQuery.md +++ b/docs/content/GroupByQuery.md @@ -49,7 +49,7 @@ There are 11 main parts to a groupBy query: |--------|-----------|---------| |queryType|This String should always be "groupBy"; this is the first thing Druid looks at to figure out how to interpret the query|yes| |dataSource|A String defining the data source to query, very similar to a table in a relational database, or a [DataSource](DataSource.html) structure.|yes| -|dimensions|A JSON list of dimensions to do the groupBy over|yes| +|dimensions|A JSON list of dimensions to do the groupBy over; or see [DimensionSpec](DimensionSpecs) for ways to extract dimensions. |yes| |limitSpec|See [LimitSpec](LimitSpec.html).|no| |having|See [Having](Having.html).|no| |granularity|Defines the granularity of the query. See [Granularities](Granularities.html)|yes|