[ 
https://issues.apache.org/jira/browse/LIVY-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

runzhiwang updated LIVY-699:
----------------------------
    Description: 
Follows are steps to reproduce the problem:
 # {{create table test(id decimal)}}.
 # {{resultSet.getMetaData().getColumnTypeName(1)}} will return string rather 
than decimal.
 # Then {{resultSet.getBigDecimal(1)}} will throw:{{ java.sql.SQLException: 
Illegal conversion}}

Additionally, SparkThrift return decimal instead of string in the same case, so 
it is necessary to return decimal instead of string in livy. The same to 
timestamp and date.

  was:
Follows are steps to reproduce the problem:
 # create table test(id decimal).
 # resultSet.getMetaData().getColumnTypeName(1) will return string rather than 
decimal, which maybe mislead user and cause error.

Additionally, SparkThrift return decimal instead of string in the same case, so 
it is necessary to return decimal instead of string in livy. The same to 
timestamp and date.


> [LIVY-699][Thrift] Fix getColumnTypeName cannot return decimal, timestamp and 
> date
> ----------------------------------------------------------------------------------
>
>                 Key: LIVY-699
>                 URL: https://issues.apache.org/jira/browse/LIVY-699
>             Project: Livy
>          Issue Type: Bug
>    Affects Versions: 0.6.0
>            Reporter: runzhiwang
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Follows are steps to reproduce the problem:
>  # {{create table test(id decimal)}}.
>  # {{resultSet.getMetaData().getColumnTypeName(1)}} will return string rather 
> than decimal.
>  # Then {{resultSet.getBigDecimal(1)}} will throw:{{ java.sql.SQLException: 
> Illegal conversion}}
> Additionally, SparkThrift return decimal instead of string in the same case, 
> so it is necessary to return decimal instead of string in livy. The same to 
> timestamp and date.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to