[
https://issues.apache.org/jira/browse/HBASE-21247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey reopened HBASE-21247:
---------------------------------
please revert this.
You can already provide a class name for something that implements WALProvider
for the config "hbase.wal.provider". It's in the code and also documented in
the javadoc for WALFactory.
{code}
* Configure which provider gets used with the configuration setting
"hbase.wal.provider". Available
* implementations:
* <ul>
* <li><em>defaultProvider</em> : whatever provider is standard for the hbase
version. Currently
* "asyncfs"</li>
* <li><em>asyncfs</em> : a provider that will run on top of an
implementation of the Hadoop
* FileSystem interface via an asynchronous
client.</li>
* <li><em>filesystem</em> : a provider that will run on top of an
implementation of the Hadoop
* FileSystem interface via HDFS's synchronous
DFSClient.</li>
* <li><em>multiwal</em> : a provider that will use multiple "filesystem" wal
instances per region
* server.</li>
* </ul>
*
* Alternatively, you may provide a custom implementation of {@link
WALProvider} by class name.
{code}
> Allow WAL Provider to be specified by configuration without explicit enum in
> Providers
> --------------------------------------------------------------------------------------
>
> Key: HBASE-21247
> URL: https://issues.apache.org/jira/browse/HBASE-21247
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: 21247.v1.txt, 21247.v2.txt, 21247.v3.txt, 21247.v4.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 introduces additional config which allows the specification of new
> WAL Provider through class name.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
