[
https://issues.apache.org/jira/browse/PHOENIX-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15483141#comment-15483141
]
Rajeshbabu Chintaguntla commented on PHOENIX-3262:
--------------------------------------------------
bq. don't think we can drop the column family if there's more than one local
index as the column families are shared. Might be an optimization if there's a
single local index.
This can be done but just worrying about concurrently creating indexes and
dropping indexes might cause problems I can give a try.
PHOENIX-1590 is really helpful in this case.
> When dropping a local index, delete the column family instead of individual
> rows.
> ---------------------------------------------------------------------------------
>
> Key: PHOENIX-3262
> URL: https://issues.apache.org/jira/browse/PHOENIX-3262
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Fix For: 4.9.0
>
>
> Currently when Phoenix drops a local index it places a delete marker for
> every single row, instead we can just drop the L#<x> column family.
> {{HBaseAdmin.deleteColumn}} in 0.98. And {{HBaseAdmin.deleteColumnFamily}} in
> 1.0+.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
