That¹s a bug to allow you drop i1 on t2. Could you please open a JIRA on that? As a workaround, you can recreate index i1 on t1 and drop it again.
-Jeffrey From: yeshwanth kumar <[email protected]> Reply-To: <[email protected]> Date: Thursday, August 14, 2014 at 7:35 AM To: <[email protected]> Subject: Drop index not checking the index associated table i had two tables, i created index on one table and dropped index by specifying other table, index was dropped succesfully, later when i tried indexing on the same table, it had thrown me error saying the index table name already exists, looks like, the reference was not updated in phoenix table, 0: jdbc:phoenix:localhost:/hbase-unsecure> create table t1( id integer not null primary key ,name char(5)); No rows affected (17.666 seconds) 0: jdbc:phoenix:localhost:/hbase-unsecure> create table t2( id integer not null primary key ,name char(5)); No rows affected (1.296 seconds) 0: jdbc:phoenix:localhost:/hbase-unsecure> CREATE INDEX i1 ON t1 (id); No rows affected (3.164 seconds) 0: jdbc:phoenix:localhost:/hbase-unsecure> DROP INDEX i1 on t2; No rows affected (2.023 seconds) any idea how to fix this issue, -yeshwanth -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
