2018-12-13 14:47:20 -05:00
---
2019-08-21 00:48:59 -04:00
id: limitspec
2020-04-15 19:12:20 -04:00
title: "Sorting and limiting (groupBy)"
2018-12-13 14:47:20 -05:00
---
2018-11-13 12:38:37 -05:00
<!--
~ Licensed to the Apache Software Foundation (ASF) under one
~ or more contributor license agreements. See the NOTICE file
~ distributed with this work for additional information
~ regarding copyright ownership. The ASF licenses this file
~ to you under the Apache License, Version 2.0 (the
~ "License"); you may not use this file except in compliance
~ with the License. You may obtain a copy of the License at
~
~ http://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing,
~ software distributed under the License is distributed on an
~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
~ KIND, either express or implied. See the License for the
~ specific language governing permissions and limitations
~ under the License.
-->
2020-04-15 19:12:20 -04:00
> Apache Druid supports two query languages: [Druid SQL](sql.md) and [native queries](querying.md).
> This document describes the native
> language. For information about sorting in SQL, refer to the [SQL documentation](sql.md#order-by).
2018-12-12 23:42:12 -05:00
2019-08-21 00:48:59 -04:00
The limitSpec field provides the functionality to sort and limit the set of results from a groupBy query. If you group by a single dimension and are ordering by a single metric, we highly recommend using [TopN Queries ](../querying/topnquery.md ) instead. The performance will be substantially better. Available options are:
2015-05-05 17:07:32 -04:00
### DefaultLimitSpec
The default limit spec takes a limit and the list of columns to do an orderBy operation over. The grammar is:
2019-08-21 00:48:59 -04:00
```json
2015-05-05 17:07:32 -04:00
{
"type" : "default",
"limit" : < integer_value > ,
"columns" : [list of OrderByColumnSpec],
}
```
#### OrderByColumnSpec
OrderByColumnSpecs indicate how to do order by operations. Each order-by condition can be a `jsonString` or a map of the following form:
2019-08-21 00:48:59 -04:00
```json
2015-05-05 17:07:32 -04:00
{
"dimension" : "< Any dimension or metric name > ",
2016-06-28 18:06:18 -04:00
"direction" : < "ascending"|"descending">,
2016-07-29 18:44:16 -04:00
"dimensionOrder" : < "lexicographic"(default)|"alphanumeric"|"strlen"|"numeric">
2015-05-05 17:07:32 -04:00
}
```
2016-07-29 18:44:16 -04:00
If only the dimension is provided (as a JSON string), the default order-by is ascending with lexicographic sorting.
2019-08-21 00:48:59 -04:00
See [Sorting Orders ](./sorting-orders.md ) for more information on the sorting orders specified by "dimensionOrder".