hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [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
Date Thu, 18 Dec 2014 04:09:14 GMT

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

Enis Soztutar updated HBASE-12437:
----------------------------------
    Fix Version/s:     (was: 0.98.4)
                       (was: 1.0.0)
                   1.1.0
                   0.98.10

> 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
>             Fix For: 0.98.10, 1.1.0
>
>         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. 
> 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)

Mime
View raw message