hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hsieh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7207) Consolidate snapshot related classes into fewer packages
Date Sat, 29 Dec 2012 00:34:12 GMT

    [ https://issues.apache.org/jira/browse/HBASE-7207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540671#comment-13540671

Jonathan Hsieh commented on HBASE-7207:

Yup.  To be more specific:

* hbase.snapshot.* has code used by both the offline and online cases, as well as export.
* hbase.master.snapshot.* has SnapshotManager and handlers plumbing for restore/clone/take
* hbase.regionserver.snapshot.* will have subprocedures and the different online flavors of
snapshot executed on the region server.

> Consolidate snapshot related classes into fewer packages
> --------------------------------------------------------
>                 Key: HBASE-7207
>                 URL: https://issues.apache.org/jira/browse/HBASE-7207
>             Project: HBase
>          Issue Type: Sub-task
>          Components: snapshots
>    Affects Versions: hbase-6055
>            Reporter: Jonathan Hsieh
>            Assignee: Jonathan Hsieh
>             Fix For: hbase-6055, 0.96.0
>         Attachments: hbase-7207.patch, pre-hbase-7207.patch
> The snapshot branch seems to have more packages with fewer classes present in each. 
We should consolidate them down to a core set.  I'm suggesting limiting it to:
> o.a.h.h.errorhandling (move o.a.h.h.server.errorhandling.** to this package) 
> o.a.h.h.procedure (eliminate procedure.member, procedure.coordinator, possibly add zk
for the zk implementation)
> o.a.h.h.snapshot (move o.a.h.h.server.snapshots.** to this package)
> o.a.h.h.master.snapshot (fold subpackages in)
> o.a.h.h.regionserver.snapshot (fold subpackges in)
> Likely move all TestSnapshotFrom* to o.a.h.h.snapshot.

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

View raw message