This is an automated email from the ASF dual-hosted git repository.
jihoonson pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-druid.git
The following commit(s) were added to refs/heads/master by this push:
new 7f89c72 Add definition of 'NONE' to queryGranularity in
ingestion.index doc (#6073)
7f89c72 is described below
commit 7f89c7293290515e98807b5479bead0f4e5913fe
Author: Caroline1000 <[email protected]>
AuthorDate: Mon Jul 30 14:07:33 2018 -0700
Add definition of 'NONE' to queryGranularity in ingestion.index doc (#6073)
* Add meaning of granularity = None to queryGranularity
* Fix format
---
docs/content/ingestion/index.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/content/ingestion/index.md b/docs/content/ingestion/index.md
index 3672a10..1529455 100644
--- a/docs/content/ingestion/index.md
+++ b/docs/content/ingestion/index.md
@@ -256,7 +256,7 @@ This spec is used to generated segments with uniform
intervals.
| Field | Type | Description | Required |
|-------|------|-------------|----------|
| segmentGranularity | string | The granularity to create segments at. | no
(default == 'DAY') |
-| queryGranularity | string | The minimum granularity to be able to query
results at and the granularity of the data inside the segment. E.g. a value of
"minute" will mean that data is aggregated at minutely granularity. That is, if
there are collisions in the tuple (minute(timestamp), dimensions), then it will
aggregate values together using the aggregators instead of storing individual
rows. | no (default == 'NONE') |
+| queryGranularity | string | The minimum granularity to be able to query
results at and the granularity of the data inside the segment. E.g. a value of
"minute" will mean that data is aggregated at minutely granularity. That is, if
there are collisions in the tuple (minute(timestamp), dimensions), then it will
aggregate values together using the aggregators instead of storing individual
rows. A granularity of 'NONE' means millisecond granularity.| no (default ==
'NONE') |
| rollup | boolean | rollup or not | no (default == true) |
| intervals | string | A list of intervals for the raw data being ingested.
Ignored for real-time ingestion. | no. If specified, batch ingestion tasks may
skip determining partitions phase which results in faster ingestion. |
@@ -266,7 +266,7 @@ This spec is used to generate segments with arbitrary
intervals (it tries to cre
| Field | Type | Description | Required |
|-------|------|-------------|----------|
-| queryGranularity | string | The minimum granularity to be able to query
results at and the granularity of the data inside the segment. E.g. a value of
"minute" will mean that data is aggregated at minutely granularity. That is, if
there are collisions in the tuple (minute(timestamp), dimensions), then it will
aggregate values together using the aggregators instead of storing individual
rows. | no (default == 'NONE') |
+| queryGranularity | string | The minimum granularity to be able to query
results at and the granularity of the data inside the segment. E.g. a value of
"minute" will mean that data is aggregated at minutely granularity. That is, if
there are collisions in the tuple (minute(timestamp), dimensions), then it will
aggregate values together using the aggregators instead of storing individual
rows. A granularity of 'NONE' means millisecond granularity.| no (default ==
'NONE') |
| rollup | boolean | rollup or not | no (default == true) |
| intervals | string | A list of intervals for the raw data being ingested.
Ignored for real-time ingestion. | no. If specified, batch ingestion tasks may
skip determining partitions phase which results in faster ingestion. |
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
