[ 
https://issues.apache.org/jira/browse/HIVE-8889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14215691#comment-14215691
 ] 

Chaoyu Tang commented on HIVE-8889:
-----------------------------------

[~glingle] I was not able to reproduce the issue using Hive provided JDBC 
driver with following test code:
{code}
        Connection con = DriverManager.getConnection(connstring, user, passwd);
        Statement stmt = con.createStatement();
      
        String sql = "select key as keyLabel, value as valLabel from src";
        ResultSet res = stmt.executeQuery(sql);        
        while (res.next()) {
            System.out.println("key: " + res.getString(1) + "; value: " + 
res.getString("valLabel"));
        }
{code}
I could get results using either getString(index) and getString(columnLabel), 
and did not see the issue you observed. If you still have this problem, could 
you provide your test code.

> 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
>
> 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