[
https://issues.apache.org/jira/browse/HBASE-18784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427886#comment-16427886
]
Hadoop QA commented on HBASE-18784:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 6s{color}
| {color:red} HBASE-18784 does not apply to branch-1. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.7.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-18784 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12896107/HBASE-18784-branch-1.v2.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/12318/console |
| Powered by | Apache Yetus 0.7.0 http://yetus.apache.org |
This message was automatically generated.
> Use of filesystem that requires hflush / hsync / append / etc should query
> outputstream capabilities
> ----------------------------------------------------------------------------------------------------
>
> Key: HBASE-18784
> URL: https://issues.apache.org/jira/browse/HBASE-18784
> Project: HBase
> Issue Type: Improvement
> Components: Filesystem Integration
> Affects Versions: 1.4.0, 2.0.0-alpha-2
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Major
> Fix For: 1.5.0, 2.0.0
>
> Attachments: HBASE-18784-branch-1.v2.patch, HBASE-18784.0.patch,
> HBASE-18784.1.patch, HBASE-18784.2.patch
>
>
> In places where we rely on the underlying filesystem holding up the promises
> of hflush/hsync (most importantly the WAL), we should use the new interfaces
> provided by HDFS-11644 to fail loudly when they are not present (e.g. on S3,
> on EC mounts, etc).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
