[
https://issues.apache.org/jira/browse/HBASE-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586183#comment-13586183
]
Elliott Clark commented on HBASE-7188:
--------------------------------------
I would:
* Split out Mapreduce code...
** This one will be the last large bit of code I can think of that needs to be
re-organized.
** Getting HFile and Wal teased out from the regionserver guts will be
interesting.
* Split usages of probuf into the respective parts, so that there's a better
dividing line of client/server:
** AdminProtobuf
** ReplicationProtobuf
** ZookeeperProtobuf
** HFileProtobuf.
* We need a test to make sure that all exceptions that a client can see are in
the client module.
* Replication zookeeper needs some work so that the admin parts are not tied to
the Server.class. (Then the server class can move back into the hbase-server
module.)
* My splitting of SnapshotDescriptionUtils might need some better naming.
** I went with ClientSnapshotDescriptionUtils
** The guys who are more involved with snapshots might want to change that.
> Move classes into hbase-client
> ------------------------------
>
> Key: HBASE-7188
> URL: https://issues.apache.org/jira/browse/HBASE-7188
> Project: HBase
> Issue Type: Sub-task
> Components: Admin, Client, IPC/RPC, Replication, snapshots
> Affects Versions: 0.96.0
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Priority: Critical
> Fix For: 0.96.0
>
> Attachments: HBASE-7188-0.patch, HBASE-7188-1.patch,
> HBASE-7188-2.patch, HBASE-7188-3.patch, HBASE-7188-5.patch,
> HBASE-7188-6.patch, HBASE-7188-7.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
