ORDER BY clause
API token hashing is enabled by default in InfluxDB OSS 2.9.0
Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — capture any plaintext tokens you still need before you upgrade.
For more information, see Token hashing.
Use the ORDER BY clause to sort data.
ORDER BY time DESC
By default, InfluxDB returns results in ascending time order; the first point
returned has the oldest timestamp and
the last point returned has the most recent timestamp.
ORDER BY time DESC reverses that order such that InfluxDB returns the points
with the most recent timestamps first.
Syntax
SELECT_clause FROM_clause [WHERE_clause] [GROUP_BY_clause] ORDER BY time DESCIf the query includes a GROUP BY clause, ORDER by time DESC must appear after the GROUP BY clause.
If the query includes a WHERE clause and no GROUP BY clause, ORDER by time DESC must appear after the WHERE clause.
Examples
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB OSS v2 and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.