[jira] [Updated] (HBASE-4132) Extend the WALObserver API to accomodate log archival

["dhruba borthakur (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

dhruba borthakur updated HBASE-4132:
------------------------------------

    Attachment: walArchive.txt

Added two new methods to the WALObserver interface:

{code}

  /**
   * 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
   */
  public void logArchiveStart(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
   */
  public void logArchiveComplete(Path oldPath, Path newPath,
    boolean archivalWasSuccessful) throws IOException;

{code}

Any backward compatibility issues I need to think about? Especially since this has been a public API. 

> Extend the WALObserver 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
>            Assignee: dhruba borthakur
>         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