[
https://issues.apache.org/jira/browse/HIVE-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-4519:
-----------------------------------
Assignee: Robert Roland
Affects Version/s: (was: 0.10.0)
Status: Open (was: Patch Available)
We should also update the corresponding java.sql.Types mapping in
service/src/java/org/apache/hive/service/cli/Type.java. I think following makes
sense:
* ARRAY => java.sql.Types.ARRAY
* MAP => java.sql.Types.JAVA_OBJECT
* STRUCT => java.sql.Types.STRUCT
* UNION => java.sql.Types.OTHER
* USER_DEFINED_TYPES => java.sql.Types.OTHER
> JDBC getColumnTypeName() should respond with the Hive-specifc type name for
> ARRAY, STRUCT and MAP
> -------------------------------------------------------------------------------------------------
>
> Key: HIVE-4519
> URL: https://issues.apache.org/jira/browse/HIVE-4519
> Project: Hive
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 0.11.0
> Reporter: Robert Roland
> Assignee: Robert Roland
> Attachments: HIVE-4519.1.patch.txt
>
>
> Per the Javadocs for ResultSetMetaData#getColumnTypeName():
> "type name used by the database. If the column type is a user-defined type,
> then a fully-qualified type name is returned."
> Hive's type for array, struct and map is not String. It is array, struct or
> map, using a JSON string serialization. Returning the Hive type here will
> allow you to programmatically determine if you should parse the value in the
> ResultSet as JSON.
> ResultSetMetaData#getColumnType() should potentially return OTHER to indicate
> the column is a database-specific return type.
> This would replace the fix provided HIVE-1378.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
