[
https://issues.apache.org/jira/browse/PHOENIX-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17273535#comment-17273535
]
ASF GitHub Bot commented on PHOENIX-6343:
-----------------------------------------
stoty commented on pull request #1118:
URL: https://github.com/apache/phoenix/pull/1118#issuecomment-769022153
That is more of an sqlline/presentation problem.
You can address the different columns via the JDBC API unambigously ( I
hope, though I didn't test this), while it's not possible in the PK vs default
CF case.
Based on this, we should only disallow the PK names in the default CF.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Phoenix allows duplicate column names when one of them is a primary key
> -----------------------------------------------------------------------
>
> Key: PHOENIX-6343
> URL: https://issues.apache.org/jira/browse/PHOENIX-6343
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Affects Versions: 5.0.0, 4.15.0
> Reporter: Istvan Toth
> Assignee: Viraj Jasani
> Priority: Major
> Fix For: 5.1.0, 4.16.1, 4.17.0
>
>
> {code:sql}
> CREATE TABLE IF NOT EXISTS test_duplicate_columns (
> name VARCHAR NOT NULL PRIMARY KEY,
> city VARCHAR, name VARCHAR);
> {code}
> {noformat}
> select * from test_duplicate_columns;
> +------+------+------+
> | NAME | CITY | NAME |
> +------+------+------+
> +------+------+------+
> No rows selected (0.015 seconds)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
