Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 29 Apr 2016 05:32:12 +0000 (UTC)
From: "Sean Busbey (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12953731.1458978433000.67300.1461907932878@Atlassian.JIRA>
In-Reply-To: <JIRA.12953731.1458978433000@Atlassian.JIRA>
References: <JIRA.12953731.1458978433000@Atlassian.JIRA>
 <JIRA.12953731.1458978433758@arcas>
Subject: [jira] [Commented] (HBASE-15536) Make AsyncFSWAL as our default WAL
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-15536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15263566#comment-15263566 ] 

Sean Busbey commented on HBASE-15536:
-------------------------------------

{quote}
bq. Maybe add a note on commit to the DefaultWALProvider about this 'odd' fact.
I think we could change the name of DefaultWALProvider to a more reasonable name, but still map 'o.a.h.h.regionserver.wal.DefaultWALProvider' to the renamed class. This does not break the config compatibility.
{quote}

We shouldn't need to do this. One motivating factor for having config enums, like the wal provider names, is so that the names of Classes aren't in our config compatibility. Folks relying on a classname should already know they're taking an unsupported route.

> Make AsyncFSWAL as our default WAL
> ----------------------------------
>
>                 Key: HBASE-15536
>                 URL: https://issues.apache.org/jira/browse/HBASE-15536
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.0.0
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>             Fix For: 2.0.0
>
>         Attachments: HBASE-15536-v1.patch, HBASE-15536-v2.patch, HBASE-15536.patch
>
>
> As it should be predicated on passing basic cluster ITBLL


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