-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Update float, half_float and scaled_float mappings #2430
Conversation
5cd7c3f
to
97d930f
Compare
}, | ||
"requests_per_sec": 0.0119197, | ||
"requests_per_sec": 0.00331858, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will be rounded to 3 digits in elasticsearch which I think is fine. @tsg WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I think that's fine.
@@ -1687,15 +1687,15 @@ Number of requested checkpoints that have been performed. | |||
[float] | |||
=== postgresql.bgwriter.checkpoints.times.write.ms | |||
|
|||
type: float | |||
type: scaled_float |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd leave these as floats because they are the total (not the derivative) number of milliseconds, so if you have an instance running for a year these numbers can be huge. Since float is what Postgres uses to report them, I'd say it's safer for us to also use floats to avoid overflows.
Left two comments, otherwise LGTM. |
97d930f
to
97e2106
Compare
@tsg new version pushed with the adjustments to postgres. |
* The mappings for float, half_float and scaled_float were reviewed and adjusted * All integers were converted to long as this was already happening automatically in the script * Json examples updated Closes elastic#2238
97e2106
to
649ebbb
Compare
Closes #2238