[
https://issues.apache.org/jira/browse/PHOENIX-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346354#comment-14346354
]
James Taylor commented on PHOENIX-1696:
---------------------------------------
I think the fix is to just remove the check for index.size() > 1. If there's
more than one column with that name, I think it's indeterminate which one gets
returned (but it's not an error). Are there any downstream effects of removing
this check, [~maryannxue]?
Perhaps we should roll a 4.3.1 with this fix plus a few others?
> 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
>
> {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)
