Skip to content
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

Archive policy back_window should be a timespan #459

Open
jd opened this issue Oct 29, 2017 · 2 comments
Open

Archive policy back_window should be a timespan #459

jd opened this issue Oct 29, 2017 · 2 comments

Comments

@jd
Copy link
Member

jd commented Oct 29, 2017

The current value is an integer representing the number of the coarsest granularity in all definitions of an AP. This is not really clear for end users. It should be a regular timespan and rounded to the higher granularity internally.

@chungg
Copy link
Member

chungg commented Oct 30, 2017

so if i have a policy of 5s and 1min (let's assume timespan is infinite). if i set 'back_window_timespan' as:

  • 6s what happens?
  • 62s what happens?

@jd
Copy link
Member Author

jd commented Nov 1, 2017

If you set 6s, then it would be rounded to 60s (equivalent to back_window = 1). If you set 62s, it'd be 120s (equivalent to back_window = 2).

The rounded timespan would be returned by the API when returning the detail of the created AP, so you know how it has been rounded.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants