[
https://issues.apache.org/jira/browse/PHOENIX-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15479226#comment-15479226
]
James Taylor commented on PHOENIX-3262:
---------------------------------------
The drop of an index goes through PostDDLCompiler which sets
BaseScannerRegionObserver.DELETE_AGG and then runs a COUNT(1) query to trigger
some code in UngroupedAggregateRegionObserver to set delete markers for each
row.
I 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. WDYT, [~rajeshbabu]?
> 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)
