2023.05

2023.05

  • Imply
  • Ingest
  • Query
  • Visualize
  • Administer
  • Deploy

›Native query components

Overview

  • Querying data
  • Datasources

    • Datasources
    • Joins
    • Lookups
    • Query execution

    Query configuration

    • Query caching
    • Using query caching
    • Query context
  • Enhanced IP support
  • Multi-value dimensions
  • Nested columns
  • Multitenancy
  • Troubleshooting

Druid SQL

  • Overview and syntax
  • SQL data types
  • Druid SQL Functions

    • All functions
    • Operators
    • Scalar functions
    • Aggregation functions
    • JSON functions
    • Multi-value string functions
  • SQL metadata tables
  • SQL query context
  • Async SQL download
  • SQL query translation
  • Druid SQL APIs

    • Druid SQL API
    • Async SQL download API
    • JDBC driver API

Native queries

  • Native queries
  • Native query types

    • Timeseries
    • TopN
    • GroupBy
    • Scan
    • Search
    • TimeBoundary
    • SegmentMetadata
    • DatasourceMetadata

    Native query components

    • Filters
    • Granularities
    • Dimensions
    • Aggregations
    • Post-aggregations
    • Expressions
    • Having filters (groupBy)
    • Sorting and limiting (groupBy)
    • Sorting (topN)
    • String comparators
    • Virtual columns
    • Spatial filters

Sorting (topN)

Apache Druid supports two query languages: Druid SQL and native queries. This document describes the native language. For information about sorting in SQL, refer to the SQL documentation.

In Apache Druid, the topN metric spec specifies how topN values should be sorted.

Numeric TopNMetricSpec

The simplest metric specification is a String value indicating the metric to sort topN results by. They are included in a topN query with:

"metric": "<metric_name>"

The metric field can also be given as a JSON object. The grammar for dimension values sorted by numeric value is shown below:

"metric": {
    "type": "numeric",
    "metric": "<metric_name>"
}
propertydescriptionrequired?
typethis indicates a numeric sortyes
metricthe actual metric field in which results will be sorted byyes

Dimension TopNMetricSpec

This metric specification sorts TopN results by dimension value, using one of the sorting orders described here: Sorting Orders

propertytypedescriptionrequired?
typeStringthis indicates a sort a dimension's valuesyes, must be 'dimension'
orderingStringSpecifies the sorting order. Can be one of the following values: "lexicographic", "alphanumeric", "numeric", "strlen". See Sorting Orders for more details.no, default: "lexicographic"
previousStopStringthe starting point of the sort. For example, if a previousStop value is 'b', all values before 'b' are discarded. This field can be used to paginate through all the dimension values.no

The following metricSpec uses lexicographic sorting.

"metric": {
    "type": "dimension",
    "ordering": "lexicographic",
    "previousStop": "<previousStop_value>"
}

Note that in earlier versions of Druid, the functionality provided by the DimensionTopNMetricSpec was handled by two separate spec types, Lexicographic and Alphanumeric (when only two sorting orders were supported). These spec types have been deprecated but are still usable.

Inverted TopNMetricSpec

Sort dimension values in inverted order, i.e inverts the order of the delegate metric spec. It can be used to sort the values in ascending order.

"metric": {
    "type": "inverted",
    "metric": <delegate_top_n_metric_spec>
}
propertydescriptionrequired?
typethis indicates an inverted sortyes
metricthe delegate metric spec.yes
Last updated on 11/17/2022
← Sorting and limiting (groupBy)String comparators →
  • Numeric TopNMetricSpec
  • Dimension TopNMetricSpec
  • Inverted TopNMetricSpec
2023.05
Key links
Try ImplyApache Druid siteImply GitHub
Get help
Stack OverflowSupportContact us
Learn more
Apache Druid forumsBlog
Copyright © 2023 Imply Data, Inc