[
https://issues.apache.org/jira/browse/HBASE-14888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085023#comment-15085023
]
Anoop Sam John commented on HBASE-14888:
----------------------------------------
{quote}
This patch changes the semantic around namespace create/delete/modify when
coprocessor asks that the invocation be by-passed. Previous the by-pass was
done silently -- the method would just return with no indication as to whether
by-pass route had been taken or not. This patch adds throwing of a
BypassCoprocessorException which is thrown if we have been asked to bypass a
call.
{quote}
Normally when the CP pre hook says to bypass, we bypass the actual op. The DML
ops are like that. DDL op when checked, the createTable seems just not
considering the value at all. The addColumn seems bypassing the add op. How
can we have a consistent behavior?
> ClusterSchema: Add Namespace Operations
> ---------------------------------------
>
> Key: HBASE-14888
> URL: https://issues.apache.org/jira/browse/HBASE-14888
> Project: HBase
> Issue Type: Sub-task
> Components: API
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0
>
> Attachments:
> 0001-Add-in-a-ClusterSchema-Interface.-It-will-have-all-Av2.patch,
> 14888.patch, 14888.v8.txt, 14888v11.patch, 14888v12.patch, 14888v13.patch,
> 14888v14.patch, 14888v15.patch, 14888v16.patch, 14888v17.txt, 14888v18.patch,
> 14888v19.patch, 14888v20.patch, 14888v22.patch, 14888v23.patch,
> 14888v24.patch, 14888v3.txt, 14888v4.txt, 14888v5.txt, 14888v6.txt,
> 14888v7.txt, 14888v9.txt, test.patch
>
>
> Add in a ClusterSchema Interface. It will have all API for all cluster
> manipulation; adding namespaces, tables, amending column families, etc. The
> idea is to gather up our mess and put it all behind a tidy API that all works
> the same way whatever you changing returning a Future to wait on and behind
> the scenes driving Procedures.
> This patch does namespace operations first.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
