| id | title |
|---|---|
sorting-orders |
String comparators |
Apache Druid supports two query languages: Druid SQL and native queries. This document describes the native language. For information about functions available in SQL, refer to the SQL documentation.
These sorting orders are used by the TopNMetricSpec, SearchQuery, GroupByQuery's LimitSpec, and BoundFilter.
Sorts values by converting Strings to their UTF-8 byte array representations and comparing lexicographically, byte-by-byte.
Suitable for strings with both numeric and non-numeric content, e.g.: "file12 sorts after file2"
See https://github.com/amjjd/java-alphanum for more details on how this ordering sorts values.
This ordering is not suitable for numbers with decimal points or negative numbers.
- For example, "1.3" precedes "1.15" in this ordering because "15" has more significant digits than "3".
- Negative numbers are sorted after positive numbers (because numeric characters precede the "-" in the negative numbers).
Sorts values as numbers, supports integers and floating point values. Negative values are supported.
This sorting order will try to parse all string values as numbers. Unparseable values are treated as nulls, and nulls precede numbers.
When comparing two unparseable values (e.g., "hello" and "world"), this ordering will sort by comparing the unparsed strings lexicographically.
Sorts values by their string lengths. When there is a tie, this comparator falls back to using the String compareTo method.
Sorts values as versions, e.g.: "10.0 sorts after 9.0", "1.0.0-SNAPSHOT sorts after 1.0.0".
See https://maven.apache.org/ref/3.6.0/maven-artifact/apidocs/org/apache/maven/artifact/versioning/ComparableVersion.html for more details on how this ordering sorts values.