[
https://issues.apache.org/jira/browse/HIVE-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080816#comment-13080816
]
Mythili Gopalakrishnan commented on HIVE-1631:
----------------------------------------------
Just verified this fix and does not work correctly. Here are my findings on a
FLOAT column
Without Patch on a FLOAT Column
--------------------------------
DatabaseMetaData.getColumns () COLUMN_SIZE returns 12
DatabaseMetaData.getColumns () DECIMAL_DIGITS - returns 0
ResultSetMetaData.getPrecision() returns 0
ResultSetMetaData.getScale() returns 0
With Patch on a FLOAT Column
----------------------------
DatabaseMetaData.getColumns () COLUMN_SIZE returns 24
DatabaseMetaData.getColumns () DECIMAL_DIGITS - returns 0
ResultSetMetaData.getPrecision() returns 0
ResultSetMetaData.getScale() returns 0
Both DatabaseMetadata and ResultSet metadata must return the same information
for Precision and Scale for FLOAT,DOUBLE types.
> JDBC driver returns wrong precision, scale, or column size for some data types
> ------------------------------------------------------------------------------
>
> Key: HIVE-1631
> URL: https://issues.apache.org/jira/browse/HIVE-1631
> Project: Hive
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 0.7.0
> Reporter: Steven Wong
> Assignee: Patrick Hunt
> Priority: Minor
> Fix For: 0.8.0
>
> Attachments: HIVE-1631.patch
>
>
> For some data types, these methods return values that do not conform to the
> JDBC spec:
> org.apache.hadoop.hive.jdbc.HiveResultSetMetaData.getPrecision(int)
> org.apache.hadoop.hive.jdbc.HiveResultSetMetaData.getScale(int)
> org.apache.hadoop.hive.jdbc.HiveResultSetMetaData.getColumnDisplaySize(int)
> org.apache.hadoop.hive.jdbc.JdbcColumn.getColumnSize()
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
