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

stringFirst and stringLast supported in ingestion (#12466)

This commit is contained in:
Victoria Lim 2022-04-21 19:28:49 -07:00 committed by GitHub
parent f95447070e
commit 63a993c33a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/querying/aggregations.md
View File

@ -43,9 +43,9 @@ The following sections list the available aggregate functions. Unless otherwise
{ "type" : "count", "name" : <output_name> } { "type" : "count", "name" : <output_name> }
``` ```
Please note the count aggregator counts the number of Druid rows, which does not always reflect the number of raw events ingested. The `count` aggregator counts the number of Druid rows, which does not always reflect the number of raw events ingested.
This is because Druid can be configured to roll up data at ingestion time. To This is because Druid can be configured to roll up data at ingestion time. To
count the number of ingested rows of data, include a count aggregator at ingestion time, and a longSum aggregator at count the number of ingested rows of data, include a `count` aggregator at ingestion time and a `longSum` aggregator at
query time. query time.
### Sum aggregators ### Sum aggregators
@ -58,8 +58,9 @@ Computes the sum of values as a 64-bit, signed integer.
{ "type" : "longSum", "name" : <output_name>, "fieldName" : <metric_name> } { "type" : "longSum", "name" : <output_name>, "fieldName" : <metric_name> }
``` ```
`name` – output name for the summed value The `longSum` aggregator takes the following properties:
`fieldName` – name of the metric column to sum over * `name`: Output name for the summed value
* `fieldName`: Name of the metric column to sum over
#### `doubleSum` aggregator #### `doubleSum` aggregator
@ -77,7 +78,7 @@ Computes and stores the sum of values as a 32-bit floating point value. Similar
{ "type" : "floatSum", "name" : <output_name>, "fieldName" : <metric_name> } { "type" : "floatSum", "name" : <output_name>, "fieldName" : <metric_name> }
``` ```
### Min / Max aggregators ### Min and max aggregators
#### `doubleMin` aggregator #### `doubleMin` aggregator
@ -137,11 +138,14 @@ To accomplish mean aggregation on ingestion, refer to the [Quantiles aggregator]
{ "type" : "doubleMean", "name" : <output_name>, "fieldName" : <metric_name> } { "type" : "doubleMean", "name" : <output_name>, "fieldName" : <metric_name> }
``` ```
### First / Last aggregator ### First and last aggregators
(Double/Float/Long) Do not use First and Last aggregators in an ingestion spec. They are only supported for queries. The first and last aggregators determine the metric values that respectively correspond to the earliest and latest values of a time column.
Note that queries with first/last aggregators on a segment created with rollup enabled return the rolled up value, and not the last value within the raw ingested data. Do not use first and last aggregators for the double, float, and long types in an ingestion spec. They are only supported for queries.
The string-typed aggregators, `stringFirst` and `stringLast`, are supported for both ingestion and querying.
Queries with first or last aggregators on a segment created with rollup return the rolled up value, not the first or last value from the raw ingested data.
#### `doubleFirst` aggregator #### `doubleFirst` aggregator
@ -251,7 +255,7 @@ Note that queries with first/last aggregators on a segment created with rollup e
} }
``` ```
### ANY aggregator ### ANY aggregators
(Double/Float/Long/String) ANY aggregator cannot be used in ingestion spec, and should only be specified as part of queries. (Double/Float/Long/String) ANY aggregator cannot be used in ingestion spec, and should only be specified as part of queries.