[ https://issues.apache.org/jira/browse/HBASE-14448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900976#comment-14900976 ]
Hudson commented on HBASE-14448: -------------------------------- SUCCESS: Integrated in HBase-1.3-IT #169 (See [https://builds.apache.org/job/HBase-1.3-IT/169/]) HBASE-14448 Refine RegionGroupingProvider Phase-2: remove provider nesting and formalize wal group name (Yu Li) (tedyu: rev 81d04cde275addcef5730943721c0f3601f74a72) * hbase-server/src/main/java/org/apache/hadoop/hbase/wal/DefaultWALProvider.java * hbase-server/src/main/java/org/apache/hadoop/hbase/wal/BoundedGroupingStrategy.java * hbase-server/src/main/java/org/apache/hadoop/hbase/wal/RegionGroupingProvider.java > Refine RegionGroupingProvider Phase-2: remove provider nesting and formalize > wal group name > ------------------------------------------------------------------------------------------- > > Key: HBASE-14448 > URL: https://issues.apache.org/jira/browse/HBASE-14448 > Project: HBase > Issue Type: Improvement > Reporter: Yu Li > Assignee: Yu Li > Fix For: 2.0.0, 1.3.0 > > Attachments: HBASE-14448.patch, HBASE-14448_v2.patch, > HBASE-14448_v3.patch > > > Now we are nesting DefaultWALProvider inside RegionGroupingProvider, which > makes the logic ambiguous since a "provider" itself should provide logs. > Suggest to directly instantiate FSHlog in RegionGroupingProvider. > W.r.t wal group name, now in RegionGroupingProvider it's using sth like > "<factoryId>\-null\-<randomUUID>" which is quite long and unnecessary. > Suggest to directly use "<providerId>.<groupName>". > For more details, please refer to the initial patch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)