Apache
/
druid
mirror of https://github.com/apache/druid.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #398 from metamx/igalDruid 

minor tweaking to clarify instructions for csv and tsv
This commit is contained in:
fjy 2014-02-14 12:52:07 -07:00
parent 4b902aed23 5ee776db64
commit 5607edb813
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/content/Data_formats.md
View File

@ -63,7 +63,7 @@ If you use the [indexing service](Indexing-Service.html) for ingesting the data,
Specified here are the location of the datafile, the timestamp column, the format of the data, and the columns that will become dimensions in Druid.
Since the CSV data does not contain the column names, they will have to be added before that data can be processed:
Since the CSV data cannot contain the column names (no header is allowed), these must be added before that data can be processed:
```json
"firehose" : {

4
docs/content/TimeseriesQuery.md
View File

@ -52,7 +52,7 @@ There are 7 main parts to a timeseries query:
|granularity|Defines the granularity of the query. See [Granularities](Granularities.html)|yes|
|filter|See [Filters](Filters.html)|no|
|aggregations|See [Aggregations](Aggregations.html)|yes|
|postAggregations|See [Post Aggregations](Post-Aggregations.html)|no|
|postAggregations|See [Post Aggregations](Post-aggregations.html)|no|
|intervals|A JSON Object representing ISO-8601 Intervals. This defines the time ranges to run the query over.|yes|
|context|An additional JSON Object which can be used to specify certain flags.|no|
@ -69,4 +69,4 @@ To pull it all together, the above query would return 2 data points, one for eac
"result": { "sample_name1": <some_value>, "sample_name2": <some_value>, "sample_divide": <some_value> }
}
]
```
```