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

Chaoyu Tang updated HIVE-8889:
------------------------------
    Attachment: HIVE-8889.2.patch

Limited the patch change only in JDBC so that its ResultSet.getXXX is still 
able to use shortname to get result for query select *  when HS2 
hive.resultset.use.unique.column.names is set to true.

To support getXXX using either shortname or qualified name for all queries 
needs more and complicated change in Hive which will be tracked in a new JIRA. 


> JDBC Driver ResultSet.getXXXXXX(String columnLabel) methods Broken
> ------------------------------------------------------------------
>
>                 Key: HIVE-8889
>                 URL: https://issues.apache.org/jira/browse/HIVE-8889
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.13.1
>            Reporter: G Lingle
>            Assignee: Chaoyu Tang
>            Priority: Critical
>             Fix For: 0.15.0, 0.14.1
>
>         Attachments: HIVE-8889.1.patch, HIVE-8889.2.patch, HIVE-8889.patch
>
>
> Using hive-jdbc-0.13.1-cdh5.2.0.jar.
> All of the get-by-column-label methods of HiveBaseResultSet are now broken.  
> They don't take just the column label as they should.  Instead you have to 
> pass in <table name>.<column name>.  This requirement doesn't conform to the 
> java ResultSet API which specifies:
> "columnLabel - the label for the column specified with the SQL AS clause. If 
> the SQL AS clause was not specified, then the label is the name of the column"
> Looking at the code, it seems that the problem is that findColumn() method is 
> looking in normalizedColumnNames instead of the columnNames.
> BTW, Another annoying issue with the code is that the SQLException thrown 
> gives no indication of what the problem is.  It should at least say that the 
> column name wasn't found in the description string.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to