Github user dilipbiswal commented on the issue:
https://github.com/apache/spark/pull/22450
@mgaido91
Again, this may be something to think about in 3.0 timeframe. I just
checked two databases, presto and db2. Both of them treat literals such as
`1e26` as double.
db2
====
```
db2 => describe select 1e26 from cast
Column Information
Number of columns: 1
SQL type Type length Column name Name
length
-------------------- ----------- ------------------------------
-----------
480 DOUBLE 8 1
1
db2 => describe select 1.23 from cast
Column Information
Number of columns: 1
SQL type Type length Column name Name
length
-------------------- ----------- ------------------------------
-----------
484 DECIMAL 3, 2 1
1
```
presto
=====
```
presto:default> explain select 2.34E10;
Query Plan
----------------------------------------------------------------------------------
- Output[_col0] => [expr:double]
Cost: {rows: 1 (10B), cpu: 10.00, memory: 0.00, network: 0.00}
```
Should spark do the same ? What would be the repercussions if we did that ?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
