[ https://issues.apache.org/jira/browse/HBASE-21247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659175#comment-16659175 ]
Ted Yu commented on HBASE-21247: -------------------------------- If we go the above route, there is another issue we need to solve. {code} testCustomProvider(org.apache.hadoop.hbase.wal.TestWALFactory) Time elapsed: 0.275 sec <<< ERROR! java.io.IOException: couldn't set up WALProvider at org.apache.hadoop.hbase.wal.TestWALFactory.testCustomProvider(TestWALFactory.java:754) Caused by: java.lang.NoSuchMethodException: org.apache.hadoop.hbase.wal.SyncReplicationWALProvider.<init>() at org.apache.hadoop.hbase.wal.TestWALFactory.testCustomProvider(TestWALFactory.java:754) {code} SyncReplicationWALProvider must wrap an existing provider. When {{getMetaProvider}} calls {{createProvider}}, arg-less ctor would be attempted on the provider class, resulting in the above exception. > Custom WAL Provider cannot be specified by configuration whose value is > outside the enums in Providers > ------------------------------------------------------------------------------------------------------ > > Key: HBASE-21247 > URL: https://issues.apache.org/jira/browse/HBASE-21247 > Project: HBase > Issue Type: Bug > 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.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)