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

James Taylor commented on PHOENIX-1696:
---------------------------------------

Patch is fine, but let's add a simple unit test to prevent any future 
regressions (just copy/paste Samarth's test into maybe QueryMoreIT, as that's 
where the issue turned up). FWIW, the javadoc for ResultSet mentions the 
expected behavior: 
http://docs.oracle.com/javase/6/docs/api/java/sql/ResultSet.html

bq. Column names used as input to getter methods are case insensitive. When a 
getter method is called with a column name and several columns have the same 
name, the value of the first matching column will be returned. 

> Selecting column more than once fails
> -------------------------------------
>
>                 Key: PHOENIX-1696
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1696
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 5.0.0, 4.3
>            Reporter: Samarth Jain
>            Assignee: Maryann Xue
>         Attachments: 1696.patch
>
>
> {code}
> ResultSet rs = conn.createStatement().executeQuery("SELECT undoub, undoub 
> FROM t1");
> assertTrue(rs.next());
> System.out.println(rs.getObject("undoub"));
> Stacktrace:
>  
> org.apache.phoenix.schema.AmbiguousColumnException: ERROR 502 (42702): Column 
> reference ambiguous or duplicate names. columnName=UNDOUB
>       at 
> org.apache.phoenix.compile.RowProjector.getColumnIndex(RowProjector.java:143)
>       at 
> org.apache.phoenix.jdbc.PhoenixResultSet.findColumn(PhoenixResultSet.java:167)
>       at 
> org.apache.phoenix.jdbc.PhoenixResultSet.getObject(PhoenixResultSet.java:513)
> {code}
> [~maryannxue] - do you mind taking a look? I verified that this issue started 
> happening since this checkin: 
> https://github.com/apache/phoenix/commit/b2b5788d9dd96dc5fa2f0ac0d0b2a792d9bb26b2



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

Reply via email to