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

[common] Fix FLOAT precision checking. (#4656) #4658

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

hunshenshi
Copy link

Purpose

Linked issue: close #4656

Tests

API and Format

Documentation

throw new NumberFormatException(
s + " cannot be cast to float due to precision loss");
} else {
// Validate precision by comparing the rounded value
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

float f = Float.parseFloat(s);

s + " cannot be cast to float due to precision loss");
} else {
// Validate precision by comparing the rounded value
if ((double) f == d || Math.abs(f - d) < Math.abs(d * 1e-6)) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why use "d * 1e-6"?
what about Double#compare?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. The value 1e-6 (which is 0.000001) is typically a reasonable threshold for floating-point comparisons, it's a balance between precision and practical usability.
  2. This approach helps avoid rejecting values that are within the acceptable precision for FLOAT types in databases like MySQL, while still accounting for the limitations of floating-point precision.

} else {
// Significant precision loss detected
throw new NumberFormatException(
s + " cannot be cast to FLOAT due to precision loss");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The exception message need improve. It needs to cover the comparative failure situation.

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

Successfully merging this pull request may close these issues.

[Bug] Precision Loss in castFromStringInternal for Valid Float Values (e.g., -0.0009163)
2 participants