[
https://issues.apache.org/jira/browse/HADOOP-12853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174480#comment-15174480
]
Hudson commented on HADOOP-12853:
---------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9405 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9405/])
HADOOP-12853. Change WASB documentation regarding page blob support. (cnauroth:
rev f98dff329b1f94c9f53022baf0209fc1a7aaf7c2)
* hadoop-common-project/hadoop-common/CHANGES.txt
* hadoop-tools/hadoop-azure/src/site/markdown/index.md
> Change WASB documentation regarding page blob support
> -----------------------------------------------------
>
> Key: HADOOP-12853
> URL: https://issues.apache.org/jira/browse/HADOOP-12853
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/azure
> Reporter: madhumita chakraborty
> Assignee: madhumita chakraborty
> Priority: Minor
> Fix For: 2.8.0
>
> Attachments: HADOOP-12853.001.patch
>
>
> WASB page blob support documentation in Features list at the top:
> Supports both page blobs (suitable for most use cases, such as MapReduce) and
> block blobs (suitable for continuous write use cases, such as an HBase
> write-ahead log).
> Which is actually the opposite. Block blobs are better for typical big data
> use cases, and page blobs were implemented to support the HBase WAL.
> It is also mentioned that
> "Page blobs can be used for other purposes beyond just HBase log files
> though."
> This is not strong enough because page blob has been tested only in context
> of HBase write ahead logs. They have not been broadly certified for use
> across the Hadoop ecosystem, hence is not recommended for use as a general
> purpose file-system via Hadoop cluster
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
