Adam Roberts created SPARK-13552:
------------------------------------
Summary: Incorrect data for Long.minValue in SQLQuerySuite on IBM
Java
Key: SPARK-13552
URL: https://issues.apache.org/jira/browse/SPARK-13552
Project: Spark
Issue Type: Bug
Components: SQL
Affects Versions: 2.0.0
Environment: IBM Java only, all platforms
Reporter: Adam Roberts
Priority: Minor
The Long.minValue test fails on IBM Java 8, we get the following incorrect
answer with the slightly simplified test case:
_val tester = sql(s"SELECT ${Long.MinValue} FROM testData")__
result is
_-9,223,372,041,149,743,104_ instead of _-9,223,372,036,854,775,808_ (there's
only one bit difference if we convert to binary representation).
The query looks to be parsed OK and we have a schema with the correct data in
the struct field but the BigDecimal's BigInteger is incorrect when we have a
GenericRowWithSchema.
I've identified that the problem started when SPARK-12575 was implemented and
suspect the following paragraph is important:
"Hive and the SQL Parser treat decimal literals differently. Hive will turn any
decimal into a Double whereas the SQL Parser would convert a non-scientific
decimal into a BigDecimal, and would turn a scientific decimal into a Double.
We follow Hive's behavior here. The new parser supports a big decimal literal,
for instance: 81923801.42BD, which can be used when a big decimal is needed."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
