[
https://issues.apache.org/jira/browse/PHOENIX-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17273522#comment-17273522
]
ASF GitHub Bot commented on PHOENIX-6343:
-----------------------------------------
stoty commented on pull request #1118:
URL: https://github.com/apache/phoenix/pull/1118#issuecomment-769006834
Thanks for checking.
In this case, IMO we should handle this like the standard columns.
If we allow the same name in different column families, then we should only
forbid matching names in the default CF.
If we don't allow the same name in differenct CFs, then we should forbid
matching names in all CFs.
----------------------------------------------------------------
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)
