You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2019/01/18 21:39:00 UTC
[jira] [Updated] (HBASE-21020) Determine WAL API changes for
replication
[ https://issues.apache.org/jira/browse/HBASE-21020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser updated HBASE-21020:
-------------------------------
Attachment: HBASE-21020.HBASE-20952.007.patch
> Determine WAL API changes for replication
> -----------------------------------------
>
> Key: HBASE-21020
> URL: https://issues.apache.org/jira/browse/HBASE-21020
> Project: HBase
> Issue Type: Sub-task
> Components: wal
> Reporter: Josh Elser
> Assignee: Ankit Singhal
> Priority: Major
> Fix For: HBASE-20952
>
> Attachments: HBASE-21020.HBASE-20952.001.patch, HBASE-21020.HBASE-20952.002.patch, HBASE-21020.HBASE-20952.003.patch, HBASE-21020.HBASE-20952.004.patch, HBASE-21020.HBASE-20952.005.patch, HBASE-21020.HBASE-20952.007.patch
>
>
> Spin-off of HBASE-20952.
> Ankit has started working on what he thinks a WAL API specifically for Replication should look like. In his own words:
> {quote}
> At a high level, it looks,
> * Need to abstract WAL name under WalInfo instead of Paths
> * Abstract the WalEntryStream for FileSystem and Streaming system.
> * Build WalStorage APIs to abstract operation on Wal.
> * Provide the implementation of all above through corresponding WalProvider
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)