-
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
Standardize influx CLI '--retention' type and accepted duration units #17107
Labels
Comments
@sanderson do you have any suggestion for what the description of retention period should read? While we got the hood open... |
@jsteenb2 Duration bucket will retain data |
jsteenb2
added a commit
that referenced
this issue
Mar 6, 2020
5 tasks
jsteenb2
added a commit
that referenced
this issue
Mar 6, 2020
jsteenb2
added a commit
that referenced
this issue
Mar 6, 2020
jsteenb2
added a commit
that referenced
this issue
Mar 6, 2020
@jsteenb2 from
Is the default for retentions |
0 will default to infinite retention period |
jacobmarble
pushed a commit
that referenced
this issue
Mar 12, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now, two
influx
commands accept a--retention
flag when creating a bucket.influx setup
influx bucket create
influx setup
's--retention
flag expects an integer that represents the retention period in nanoseconds.influx bucket create
expects a duration, but only in units up to hours.Proposal:
Both commands should expect the same data type for the bucket retention period. We should also accept day and week duration units.
Current behavior:
Retention flags expect different input types. The one that does expect a duration value only accepts
ns
,us
,ms
,s
, andh
.Desired behavior:
Retention flags should expect the same input type. In addition to the duration units already supported, they should also support days
d
, and potentially even weeksw
.Use case:
Better UX
The text was updated successfully, but these errors were encountered: