-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](func) Fix precision loss in ST_GeometryFromWKB coordinate parsing #46661
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
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
TPC-H: Total hot run time: 32784 ms |
|
TeamCity be ut coverage result: |
TPC-DS: Total hot run time: 195086 ms |
ClickBench: Total hot run time: 31.63 s |
|
run buildall |
TPC-H: Total hot run time: 32508 ms |
|
TeamCity be ut coverage result: |
TPC-DS: Total hot run time: 195277 ms |
ClickBench: Total hot run time: 31.44 s |
be/src/geo/geo_types.cpp
Outdated
| double value = S2LatLng::Longitude(*_point).degrees(); | ||
| // Handle values very close to integers | ||
| double rounded = round(value); | ||
| if (std::abs(value - rounded) < 1e-13) { // 使用更大的阈值 |
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.
please use english, thank you
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.
done
b3e6a7f to
c274a05
Compare
|
I will review this PR later |
|
run buildall |
TPC-H: Total hot run time: 31963 ms |
TPC-DS: Total hot run time: 188143 ms |
fa12fe9 to
d130192
Compare
|
run buildall |
TPC-H: Total hot run time: 32231 ms |
TPC-DS: Total hot run time: 187136 ms |
ClickBench: Total hot run time: 30.36 s |
|
TeamCity be ut coverage result: |
79544da to
a9848ee
Compare
|
run buildall |
TPC-H: Total hot run time: 32236 ms |
TPC-DS: Total hot run time: 188594 ms |
ClickBench: Total hot run time: 31.61 s |
11820a5 to
ea72e50
Compare
|
run buildall |
a911114 to
8973a68
Compare
|
run buildall |
zclllyybb
left a comment
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.
LGTM
|
PR approved by anyone and no changes requested. |
TPC-H: Total hot run time: 32182 ms |
TPC-DS: Total hot run time: 193752 ms |
|
TeamCity be ut coverage result: |
ClickBench: Total hot run time: 30.76 s |
HappenLee
left a comment
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.
LGTM
|
PR approved by at least one committer and no changes requested. |
…ng (#46661) ### What problem does this PR solve? Issue Number: close #46619 Root Cause: ``` 1. Unnecessary floating-point number conversions in coordinate handling: 1.1 converting double to string using absl::StrFormat 1.2 converting string back to double using std::stod each conversion caused precision loss. 2. Byte order handling issue in WKB parsing: 2.1 using machine endian before properly reading WKB byte order flag 2.2 this caused incorrect interpretation of coordinate values ``` Solution: ``` 1. Remove unnecessary coordinate value conversions: 1.1 directly use S2LatLng's degrees() value without string formatting 1.2 increase output precision in print_s2point to 15 digits 2. Fix WKB byte order handling: 2.1 read byte order flag first 2.2 set correct byte order before parsing coordinates ``` Result: before: ``` POINT (1.461652102e-231 3.34424828009e-59) ``` after: ``` POINT(117.194767000297 36.46326301008) ```
…ng (#46661) ### What problem does this PR solve? Issue Number: close #46619 Root Cause: ``` 1. Unnecessary floating-point number conversions in coordinate handling: 1.1 converting double to string using absl::StrFormat 1.2 converting string back to double using std::stod each conversion caused precision loss. 2. Byte order handling issue in WKB parsing: 2.1 using machine endian before properly reading WKB byte order flag 2.2 this caused incorrect interpretation of coordinate values ``` Solution: ``` 1. Remove unnecessary coordinate value conversions: 1.1 directly use S2LatLng's degrees() value without string formatting 1.2 increase output precision in print_s2point to 15 digits 2. Fix WKB byte order handling: 2.1 read byte order flag first 2.2 set correct byte order before parsing coordinates ``` Result: before: ``` POINT (1.461652102e-231 3.34424828009e-59) ``` after: ``` POINT(117.194767000297 36.46326301008) ```
…ng (apache#46661) ### What problem does this PR solve? Issue Number: close apache#46619 Root Cause: ``` 1. Unnecessary floating-point number conversions in coordinate handling: 1.1 converting double to string using absl::StrFormat 1.2 converting string back to double using std::stod each conversion caused precision loss. 2. Byte order handling issue in WKB parsing: 2.1 using machine endian before properly reading WKB byte order flag 2.2 this caused incorrect interpretation of coordinate values ``` Solution: ``` 1. Remove unnecessary coordinate value conversions: 1.1 directly use S2LatLng's degrees() value without string formatting 1.2 increase output precision in print_s2point to 15 digits 2. Fix WKB byte order handling: 2.1 read byte order flag first 2.2 set correct byte order before parsing coordinates ``` Result: before: ``` POINT (1.461652102e-231 3.34424828009e-59) ``` after: ``` POINT(117.194767000297 36.46326301008) ```
What problem does this PR solve?
Issue Number: close #46619
Root Cause:
Solution:
Result:
before:
after:
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)