[
https://issues.apache.org/jira/browse/HBASE-18893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207850#comment-16207850
]
Mike Drob commented on HBASE-18893:
-----------------------------------
Another thought I had was wondering why we have multiple code paths in master
for this? We can still keep add/delete/etc on admin for API convenience, but on
the backend maybe these all _should_ go through a ModifyTable procedure? And
then we remove the hooks around Add/Delete column entirely?
> shell 'alter' command no longer distinguishes column add/modify/delete
> ----------------------------------------------------------------------
>
> Key: HBASE-18893
> URL: https://issues.apache.org/jira/browse/HBASE-18893
> Project: HBase
> Issue Type: Bug
> Components: shell
> Reporter: Mike Drob
>
> After HBASE-15641 all 'alter' commands go through a single modifyTable call
> at the end, so we no longer can easily distinguish add, modify, and delete
> column events. This potentially affects coprocessors that needed the update
> notifications for new or removed columns.
> Let's let the shell still make separate behaviour calls like it did before
> without undoing the batching that seems pretty useful.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
