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

[Uptime] Make backend iterator class support an infinite size option #119

Closed
justinkambic opened this issue Nov 25, 2019 · 0 comments · Fixed by elastic/kibana#55931
Closed
Assignees
Labels
enhancement New feature or request

Comments

@justinkambic
Copy link

Is your feature request related to a problem? Please describe.
In elastic/kibana#48035 we introduced a very high constant value to ensure we chunk up all the monitors while counting them. It would be cleaner to patch the iterator code itself so we don't have to maintain this weird constant default.

Describe the solution you'd like
Remove the existing constant value and have the iterator support an infinite size option.

Describe alternatives you've considered
We've implemented the alternative solution.

Additional context
N/A

@justinkambic justinkambic added the enhancement New feature or request label Nov 25, 2019
@andrewvc andrewvc self-assigned this Jan 24, 2020
andrewvc added a commit to andrewvc/kibana that referenced this issue Jan 24, 2020
Fixes elastic/uptime#119

Rather than relying on a contant for the max number of monitors, it's
easier to just use infinity. This is simpler than making the iterator
more complex with an 'infinite' mode.
andrewvc added a commit to elastic/kibana that referenced this issue Jan 27, 2020
Fixes elastic/uptime#119

Rather than relying on a contant for the max number of monitors, it's
easier to just use infinity. This is simpler than making the iterator
more complex with an 'infinite' mode.

Co-authored-by: Elastic Machine <[email protected]>
andrewvc added a commit to andrewvc/kibana that referenced this issue Jan 27, 2020
Fixes elastic/uptime#119

Rather than relying on a contant for the max number of monitors, it's
easier to just use infinity. This is simpler than making the iterator
more complex with an 'infinite' mode.

Co-authored-by: Elastic Machine <[email protected]>
andrewvc added a commit to elastic/kibana that referenced this issue Jan 28, 2020
Fixes elastic/uptime#119

Rather than relying on a contant for the max number of monitors, it's
easier to just use infinity. This is simpler than making the iterator
more complex with an 'infinite' mode.

Co-authored-by: Elastic Machine <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants