You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2018/11/06 16:54:01 UTC
[jira] [Updated] (HBASE-21247) Custom Meta WAL Provider doesn't
default to custom WAL Provider whose configuration value is outside the
enums in Providers
[ https://issues.apache.org/jira/browse/HBASE-21247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated HBASE-21247:
---------------------------
Summary: Custom Meta WAL Provider doesn't default to custom WAL Provider whose configuration value is outside the enums in Providers (was: Custom WAL Provider cannot be specified by configuration whose value is outside the enums in Providers)
> Custom Meta WAL Provider doesn't default to custom WAL Provider whose configuration value is outside the enums in Providers
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-21247
> URL: https://issues.apache.org/jira/browse/HBASE-21247
> Project: HBase
> Issue Type: Bug
> Components: wal
> Affects Versions: 3.0.0, 2.2.0, 2.1.1, 2.0.2
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: 21247.v1.txt, 21247.v10.txt, 21247.v11.txt, 21247.v2.txt, 21247.v3.txt, 21247.v4.tst, 21247.v4.txt, 21247.v5.txt, 21247.v6.txt, 21247.v7.txt, 21247.v8.txt, 21247.v9.txt
>
>
> Currently all the WAL Providers acceptable to hbase are specified in Providers enum of WALFactory.
> This restricts the ability for additional WAL Providers to be supplied - by class name.
> This issue fixes the bug by allowing the specification of new WAL Provider class name using the config "hbase.wal.provider".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)