[
https://issues.apache.org/jira/browse/HBASE-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093403#comment-13093403
]
gaojinchao commented on HBASE-4132:
-----------------------------------
Whether we can add the following api?
/**
* The WAL needs to be archived. It is going to be moved from oldPath to
* newPath.
*
* @param oldPath
* the path to the old hlog
* @param newPath
* the path to the new hlog
* @return true if default behavior should be bypassed, false otherwise
*/
boolean preArchiveLog(Path oldPath, Path newPath) throws IOException;
/**
* The WAL has been archived. It is moved from oldPath to newPath.
*
* @param oldPath
* the path to the old hlog
* @param newPath
* the path to the new hlog
* @param archivalWasSuccessful
* true, if the archival was successful
*/
void postArchiveLog(Path oldPath, Path newPath,
boolean archivalWasSuccessful) throws IOException;
> Extend the WALActionsListener API to accomodate log archival
> ------------------------------------------------------------
>
> Key: HBASE-4132
> URL: https://issues.apache.org/jira/browse/HBASE-4132
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: dhruba borthakur
> Fix For: 0.92.0
>
> Attachments: walArchive.txt
>
>
> The WALObserver interface exposes the log roll events. It would be nice to
> extend it to accomodate log archival events as well.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
