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

Update float, half_float and scaled_float mappings #2430

Merged
merged 1 commit into from
Sep 2, 2016

Conversation

ruflin
Copy link
Contributor

@ruflin ruflin commented Sep 1, 2016

  • The mappings for float, half_float and scaled_float were reviewed and adjusted. All are now scaled_float
  • All integers were converted to long as this was already happening automatically in the script
  • Json examples updated

Closes #2238

},
"requests_per_sec": 0.0119197,
"requests_per_sec": 0.00331858,
Copy link
Contributor Author

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?

Copy link
Contributor

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.

@ruflin ruflin mentioned this pull request Sep 2, 2016
@@ -1687,15 +1687,15 @@ Number of requested checkpoints that have been performed.
[float]
=== postgresql.bgwriter.checkpoints.times.write.ms

type: float
type: scaled_float
Copy link
Contributor

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.

@tsg
Copy link
Contributor

tsg commented Sep 2, 2016

Left two comments, otherwise LGTM.

@ruflin
Copy link
Contributor Author

ruflin commented Sep 2, 2016

@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
@tsg tsg merged commit a3896b4 into elastic:master Sep 2, 2016
@monicasarbu monicasarbu deleted the verify-fields branch September 5, 2016 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants