hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8375) Durability setting per table
Date Wed, 28 Aug 2013 22:57:54 GMT

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

Lars Hofhansl commented on HBASE-8375:

[~enis], any assessment as to how risky this would be in 0.94? It looks like it would be backward
compatible (as long as we still also support the old option - or interpret that in terms of
the new options).
> 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
> * 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

View raw message