[
https://issues.apache.org/jira/browse/HBASE-14888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-14888:
--------------------------
Attachment: test.patch
Here is a patch that tries to add a TestClusterSchema that tests ClusterSchema
standalone. There is a bit of mocking going on but its not too crazy and is
kinda clean as long as we take on the change in Server so we have a
getConnection that returns Connection and then a getClusterConnection for dirty
work.
I got as far as TableNamespaceManager#isTableAssigned which asks the
AssignmentManager for its region states and then from there, gets regions of
the table..... if non-null, table is assigned. This is tenuous, not mockable,
and we should be able to do better.
Let me shave TableNamespaceManager so its more sensible. Will come back then to
this TestClusterSchema with a standalone ClusterSchema.
> 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, 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)
