-
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
show retention policies should be consistent with other queries #2761
Comments
We should support either way, but certainly +1 for the consistent manner. |
+1 |
+10 |
@dgnorton If it's not too hard to support both, that's fine. Many languages support variant commands. I don't think that we really have to if we don't want to, so for me, it's a matter of what is easiest. I support 2 versions of |
@corylanou We support 2 versions of count distinct on purpose. I think leaving |
Fixed by #3345 |
The the code to use correct SHOW retention command starting with 0.9.2 influxdata/influxdb#2761
Right now the syntax is
SHOW RETENTION POLICIES <db-name>
, butDROP RETENTION POLICY <rp-name> ON <db-name>
. For users it'sGRANT/REVOKE <privilege> ON <db-name>
I think
SHOW RETENTION POLICIES ON <db-name>
is more congruent with the other statements, and I find myself typing ON every time and then removing it when the parser complains.The text was updated successfully, but these errors were encountered: