You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2013/07/11 03:02:55 UTC
[jira] [Updated] (HBASE-8375) Durability setting per table
[ https://issues.apache.org/jira/browse/HBASE-8375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Enis Soztutar updated HBASE-8375:
---------------------------------
Summary: Durability setting per table (was: Streamline Table durability settings)
> 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