[
https://issues.apache.org/jira/browse/HBASE-8375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705819#comment-13705819
]
Hudson commented on HBASE-8375:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #609 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/609/])
HBASE-8375 Durability setting per table (Revision 1502076)
Result = FAILURE
enis :
Files :
*
/hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/HTableDescriptor.java
*
/hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Durability.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
* /hbase/trunk/hbase-server/src/main/ruby/hbase/admin.rb
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/TestHTableDescriptor.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java
> Durability setting per table
> ----------------------------
>
> Key: HBASE-8375
> URL: https://issues.apache.org/jira/browse/HBASE-8375
> Project: HBase
> Issue Type: Sub-task
> Reporter: Lars Hofhansl
> Assignee: Enis Soztutar
> Fix For: 0.98.0, 0.95.2
>
> Attachments: hbase-8375_v1.patch, hbase-8375_v2.patch,
> hbase-8375_v5.patch
>
>
> HBASE-7801 introduces the notion of per mutation fine grained durability
> settings.
> This issue is to consider and the discuss the same for the per table settings
> (i.e. what would be used if the mutation indicates USE_DEFAULT). I propose
> the following setting per table:
> * SKIP_WAL (i.e. an unlogged table)
> * ASYNC_WAL (the current deferred log flush)
> * SYNC_WAL (the current default)
> * FSYNC_WAL (for future uses of HDFS' hsync())
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
