[
https://issues.apache.org/jira/browse/HBASE-20567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477741#comment-16477741
]
stack commented on HBASE-20567:
-------------------------------
+1 for branch-2.0. My rationale is that it safe to add as it just changes to
Interface BUT defaults are provided (evidence it safe is that no other code
needed to be modified but the Interface itself and then in Master, the hookups
to make the new additions 'live'). Thanks [~mdrob]. Oh, other reason for
hbase-2.0 is that its wanted by navigator...
> Pass both old and new descriptors to pre/post hooks of modify operations for
> table and namespace
> ------------------------------------------------------------------------------------------------
>
> Key: HBASE-20567
> URL: https://issues.apache.org/jira/browse/HBASE-20567
> Project: HBase
> Issue Type: Improvement
> Reporter: Appy
> Assignee: Appy
> Priority: Major
> Attachments: HBASE-20567.master.001.patch,
> HBASE-20567.master.002.patch
>
>
> In postModify* hooks like {{postModifyX(..., Descriptor newDesc)}}, there's
> no way of getting the old descriptor which was there before modification
> happened.
> Having both old and new descriptors will make the hooks more useful.
> We felt the need when we wanted to audit certain events but there was no way
> of deducing them by just seeing 'after-state' of modification.
> To keep the method signatures consistent, i have modified both pre and post
> hooks with new arguments which are well named and commented.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
