jihoonson closed pull request #6073: Add definition of 'NONE' to 
queryGranularity in ingestion.index doc
URL: https://github.com/apache/incubator-druid/pull/6073
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/docs/content/ingestion/index.md b/docs/content/ingestion/index.md
index b533db622a0..9713c502ca8 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. | yes for batch, no for real-time |
 
@@ -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. | yes for batch, no for real-time |
 


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to