[jira] [Updated] (HBASE-12437) HLogFactory should be able to accept multiple custom WALReaders in case of failure to read WAL logs due to upgrade/migrate of hbase

["Enoch Hsu (JIRA)" <ji...@apache.org>]

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

Enoch Hsu updated HBASE-12437:
------------------------------
    Summary: HLogFactory should be able to accept multiple custom WALReaders in case of failure to read WAL logs due to upgrade/migrate of hbase  (was: HLogFactory does not allow fall back of custom WALReader in case of failure to read WAL logs due to upgrade/migrate of hbase)

> HLogFactory should be able to accept multiple custom WALReaders in case of failure to read WAL logs due to upgrade/migrate of hbase
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-12437
>                 URL: https://issues.apache.org/jira/browse/HBASE-12437
>             Project: HBase
>          Issue Type: Bug
>          Components: wal
>    Affects Versions: 0.96.0, 0.98.4
>            Reporter: Enoch Hsu
>            Assignee: Enoch Hsu
>             Fix For: 1.0.0, 0.98.4
>
>         Attachments: HBASE_12437.patch
>
>
> The HLogFactory createReader function allows the user to create their own reader and just assumes that the reader will work correctly. 
> The default implementation checks between Protobuf and sequencefiles. However, the custom reader option does not account for any differences in the files. In the case that I used an old custom reader for sequence files and now am using a custom reader for protobuf there should be an option for hbase to choose which reader to use based on the file.
> There should be an option or configuration to specify multiple custom readers in the case that an old custom reader was used for sequence files and and a custom reader is being used for protobuf instead of throwing an IPBRE
> The current HLogFactory does not allow me to fall back and handle upgraded file systems similar to the default case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)