[
https://issues.apache.org/jira/browse/PHOENIX-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Hacker resolved PHOENIX-1029.
----------------------------------
Resolution: Cannot Reproduce
> Duplicate column incorrectly reported during index creation
> -----------------------------------------------------------
>
> Key: PHOENIX-1029
> URL: https://issues.apache.org/jira/browse/PHOENIX-1029
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 3.0.0, 4.0.0
> Reporter: James Taylor
> Assignee: Dave Hacker
> Attachments: 1029verification.patch
>
>
> When creating an index, the system complains that a duplicate column name
> exists when you include the PK columns in the INCLUDE section. The workaround
> is to not include them, as they're automatically included.
> To repro, issue the following commands:
> {code}
> CREATE TABLE IF NOT EXISTS EVENT.APEX_LIMIT (
> ORGANIZATION_ID CHAR(15) NOT NULL,
> EVENT_TIME DATE NOT NULL,
> USER_ID CHAR(15) NOT NULL,
> ENTRY_POINT_ID CHAR(15) NOT NULL,
> ENTRY_POINT_TYPE CHAR(2) NOT NULL,
> APEX_LIMIT_ID CHAR(15) NOT NULL,
> USERNAME CHAR(80),
> NAMESPACE_PREFIX VARCHAR,
> ENTRY_POINT_NAME VARCHAR,
> EXECUTION_UNIT_NO VARCHAR,
> LIMIT_TYPE VARCHAR,
> LIMIT_VALUE DOUBLE
> CONSTRAINT PK PRIMARY KEY
> (
> ORGANIZATION_ID,
> EVENT_TIME,
> USER_ID,
> ENTRY_POINT_ID,
> ENTRY_POINT_TYPE,
> APEX_LIMIT_ID
> )
> ) VERSIONS=1,MULTI_TENANT=true, SALT_BUCKETS=64;
> CREATE INDEX IF NOT EXISTS IEAPEX_LIMIT_TIME_VALUE
> ON EVENT.APEX_LIMIT (EVENT_TIME, LIMIT_VALUE)
> INCLUDE (
> ORGANIZATION_ID,
> USER_ID,
> USERNAME,
> ENTRY_POINT_ID,
> NAMESPACE_PREFIX,
> ENTRY_POINT_NAME,
> EXECUTION_UNIT_NO,
> ENTRY_POINT_TYPE,
> LIMIT_TYPE);
> {code}
> The following error message should not be produced:
> Error: ERROR 514 (42892): A duplicate column name was detected in the object
> definition or ALTER TABLE statement. (state=42892,code=514)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
