-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
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
[0.9.4.1] current vs. intended behavior of LIMIT and possibly broken SLIMIT #4232
Comments
This is because you don't have a |
The behavior is a bit odd and we may want to consider revisiting it when we start the development cycle for 1.0. I say that one because we don't want to make a breaking change before then. |
@pauldix is there a document describing the intended behavior of LIMIT and SLIMIT? |
@beckettsean I'm going to continue here, as #4271 has been closed. Referring to the docs (https://influxdb.com/docs/v0.9/query_language/data_exploration.html#limiting-results-per-measurement) I shouldn't be forced to use a
|
Same thing in |
Is it confirmed to be broken? I do not see SLIMIT working nor with 9.6.1 neither with 10.3.1 (GROUP BY is used in query). |
Please try this again with the latest version. |
LIMIT
currently limits the number of results returned per the specified measurement:where
location
is a tag. Not sure ifLIMIT
is meant to return N points per series.SLIMIT
currently returns the same thing asSELECT *
:The text was updated successfully, but these errors were encountered: