--- layout: doc_page --- # Post-Aggregations Post-aggregations are specifications of processing that should happen on aggregated values as they come out of Druid. If you include a post aggregation as part of a query, make sure to include all aggregators the post-aggregator requires. There are several post-aggregators available. ### Arithmetic post-aggregator The arithmetic post-aggregator applies the provided function to the given fields from left to right. The fields can be aggregators or other post aggregators. Supported functions are `+`, `-`, `*`, `/`, and `quotient`. **Note**: * `/` division always returns `0` if dividing by`0`, regardless of the numerator. * `quotient` division behaves like regular floating point division Arithmetic post-aggregators may also specify an `ordering`, which defines the order of resulting values when sorting results (this can be useful for topN queries for instance): - If no ordering (or `null`) is specified, the default floating point ordering is used. - `numericFirst` ordering always returns finite values first, followed by `NaN`, and infinite values last. The grammar for an arithmetic post aggregation is: ```json postAggregation : { "type" : "arithmetic", "name" : , "fn" : , "fields": [, , ...], "ordering" : } ``` ### Field accessor post-aggregator This returns the value produced by the specified [aggregator](Aggregations.html). `fieldName` refers to the output name of the aggregator given in the [aggregations](Aggregations.html) portion of the query. ```json { "type" : "fieldAccess", "fieldName" : } ``` ### Constant post-aggregator The constant post-aggregator always returns the specified value. ```json { "type" : "constant", "name" : , "value" : } ``` ### JavaScript post-aggregator Applies the provided JavaScript function to the given fields. Fields are passed as arguments to the JavaScript function in the given order. ```json postAggregation : { "type": "javascript", "name": , "fieldNames" : [, , ...], "function": } ``` Example JavaScript aggregator: ```json { "type": "javascript", "name": "absPercent", "fieldNames": ["delta", "total"], "function": "function(delta, total) { return 100 * Math.abs(delta) / total; }" } ``` ### HyperUnique Cardinality post-aggregator The hyperUniqueCardinality post aggregator is used to wrap a hyperUnique object such that it can be used in post aggregations. ```json { "type" : "hyperUniqueCardinality", "fieldName" : } ``` It can be used in a sample calculation as so: ```json "aggregations" : [{ {"type" : "count", "name" : "rows"}, {"type" : "hyperUnique", "name" : "unique_users", "fieldName" : "uniques"} }], "postAggregations" : { "type" : "arithmetic", "name" : "average_users_per_row", "fn" : "/", "fields" : [ { "type" : "hyperUniqueCardinality", "fieldName" : "unique_users" }, { "type" : "fieldAccess", "name" : "rows", "fieldName" : "rows" } ] } ``` #### Example Usage In this example, let’s calculate a simple percentage using post aggregators. Let’s imagine our data set has a metric called "total". The format of the query JSON is as follows: ```json { ... "aggregations" : [ { "type" : "count", "name" : "rows" }, { "type" : "doubleSum", "name" : "tot", "fieldName" : "total" } ], "postAggregations" : { "type" : "arithmetic", "name" : "average", "fn" : "*", "fields" : [ { "type" : "arithmetic", "name" : "div", "fn" : "/", "fields" : [ { "type" : "fieldAccess", "name" : "tot", "fieldName" : "tot" }, { "type" : "fieldAccess", "name" : "rows", "fieldName" : "rows" } ] }, { "type" : "constant", "name": "const", "value" : 100 } ] } ... } ```