-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
feat: support scientific notation in parse_float_as_decimal
#8494
Closed
Closed
Changes from 5 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
b325670
support scientific notation
Weijun-H b64e41b
parse number to i16
Weijun-H 48fd865
use BigDecimal
Weijun-H c6d6e28
fix ci
Weijun-H 5098b17
fix ci
Weijun-H b04084a
fix ci
Weijun-H b50d5c1
fix ci
Weijun-H File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -147,7 +147,7 @@ select .0 as c1, 0. as c2, 0000. as c3, 00000.00 as c4 | |
query TTTT | ||
select arrow_typeof(.0) as c1, arrow_typeof(0.) as c2, arrow_typeof(0000.) as c3, arrow_typeof(00000.00) as c4 | ||
---- | ||
Decimal128(1, 1) Decimal128(1, 0) Decimal128(1, 0) Decimal128(2, 2) | ||
Decimal128(2, 1) Decimal128(1, 0) Decimal128(1, 0) Decimal128(3, 2) | ||
Weijun-H marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
query RR | ||
select 999999999999999999999999999999999999, -999999999999999999999999999999999999 | ||
|
@@ -193,19 +193,31 @@ select arrow_typeof(00009999999999999999999999999999999999.9999), | |
Decimal128(38, 4) Decimal128(38, 4) Decimal128(20, 0) | ||
|
||
# precision overflow | ||
statement error DataFusion error: SQL error: ParserError\("Cannot parse 123456789012345678901234567890123456789 as i128 when building decimal: precision overflow"\) | ||
statement error DataFusion error: SQL error: ParserError\("Cannot parse 123456789.012345678901234567890123456789 as i128 when building decimal: precision overflow"\) | ||
select 123456789.012345678901234567890123456789 | ||
|
||
statement error SQL error: ParserError\("Cannot parse 123456789012345678901234567890123456789 as i128 when building decimal: precision overflow"\) | ||
statement error SQL error: ParserError\("Cannot parse 123456789.012345678901234567890123456789 as i128 when building decimal: precision overflow"\) | ||
select -123456789.012345678901234567890123456789 | ||
|
||
# can not fit in i128 | ||
statement error SQL error: ParserError\("Cannot parse 1234567890123456789012345678901234567890 as i128 when building decimal: number too large to fit in target type"\) | ||
statement error SQL error: ParserError\("Cannot parse 123456789.0123456789012345678901234567890 as i128 when building decimal: precision overflow"\) | ||
select 123456789.0123456789012345678901234567890 | ||
|
||
statement error SQL error: ParserError\("Cannot parse 1234567890123456789012345678901234567890 as i128 when building decimal: number too large to fit in target type"\) | ||
statement error SQL error: ParserError\("Cannot parse 123456789.0123456789012345678901234567890 as i128 when building decimal: precision overflow"\) | ||
select -123456789.0123456789012345678901234567890 | ||
|
||
# scientific notation | ||
query RRRR | ||
select 1.234e2, 1.234e-2, -1.234e2, -1.234e-2 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
---- | ||
123.4 0.01234 -123.4 -0.01234 | ||
|
||
statement error DataFusion error: SQL error: ParserError\("Cannot parse 1.234e-40 as i128 when building decimal: precision overflow"\) | ||
select 1.234e-40 | ||
|
||
statement error DataFusion error: SQL error: ParserError\("Cannot parse 12340000000000000000000000000000000000000 as i128 when building decimal: number too large to fit in target type"\) | ||
select 1.234e+40 | ||
|
||
# Restore option to default value | ||
statement ok | ||
set datafusion.sql_parser.parse_float_as_decimal = false; |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Once you have parsed the data into a BigDecimal, I think you could just convert to a
i128
directly which would be more performant and I think potentially more correctPerhaps you could use
https://docs.rs/bigdecimal/latest/bigdecimal/struct.BigDecimal.html#method.fractional_digit_count to get the scale
And then compute the precision and the
i128
fromhttps://docs.rs/bigdecimal/latest/bigdecimal/struct.BigDecimal.html#method.into_bigint_and_exponent