We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testing on 6.6.0.
Consider using SQL to query for a 1-minute histogram, e.g. across a default metricbeat index (and the default time field, @timestamp).
@timestamp
GET /_xpack/sql?format=txt { "query": """ SELECT HISTOGRAM("@timestamp", INTERVAL 1 MINUTE) AS h FROM "metricbeat-*" GROUP BY h """ }
This correctly returns. However, when omitting GROUP BY ... as in:
GROUP BY ...
GET /_xpack/sql?format=txt { "query": """ SELECT HISTOGRAM("@timestamp", INTERVAL 1 MINUTE) FROM "metricbeat-*" """ }
We get:
{ "error": { "root_cause": [ { "type": "sql_illegal_argument_exception", "reason": "Unknown output attribute HISTOGRAM(@timestamp){g->2644358}#2644358" } ], "type": "sql_illegal_argument_exception", "reason": "Unknown output attribute HISTOGRAM(@timestamp){g->2644358}#2644358" }, "status": 500 }
We should clean up the error here so it's easier for a user to understand what they've done wrong.
The text was updated successfully, but these errors were encountered:
Pinging @elastic/es-search
Sorry, something went wrong.
master(7.0.0): 6968f09 6.x (6.7.0): 4cf0391 6.6 (6.6.1): d05c24c
No branches or pull requests
Testing on 6.6.0.
Consider using SQL to query for a 1-minute histogram, e.g. across a default metricbeat index (and the default time field,
@timestamp
).This correctly returns. However, when omitting
GROUP BY ...
as in:We get:
We should clean up the error here so it's easier for a user to understand what they've done wrong.
The text was updated successfully, but these errors were encountered: