[PHOENIX-2783] Creating secondary index with duplicated columns makes the catalog corrupted

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 4.7.0
• Assignee: Sergey Soldatov
• Reporter: Sergey Soldatov
• Created: 18/Mar/16 08:28
• Updated: 04/Oct/16 01:03
• Resolved: 04/Oct/16 00:52

Description

Simple example

create table x (t1 varchar primary key, t2 varchar, t3 varchar);
create index idx on x (t2) include (t1,t3,t3);

cause an exception that duplicated column was detected, but the client updates the catalog before throwing it and makes it unusable. All following attempt to use table x cause an exception ArrayIndexOutOfBounds. This problem was discussed on the user list recently.
The cause of the problem is that check for duplicated columns happen in PTableImpl after MetaDataClient complete the server createTable.
The simple way to fix is to add a similar check in MetaDataClient before createTable is called.
Possible someone can suggest a more elegant way to fix it?