[
https://issues.apache.org/jira/browse/HADOOP-8365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278667#comment-13278667
]
Harsh J commented on HADOOP-8365:
---------------------------------
Eli,
One clarification post the HADOOP-8320 ones, for this particular part in the
description:
bq. The sync method itself will still be available and have a broken
implementation as that was the behavior before HADOOP-8230.
But sync() does not have a broken implementation as has been shown from its
users. I do not understand that sentence completely, as HADOOP-8230 did not
change any sync()-related code, so whatever was _working_ or _broken_ before is
still the very same and will be even after what this issue aims to change.
> Provide ability to disable working sync
> ---------------------------------------
>
> Key: HADOOP-8365
> URL: https://issues.apache.org/jira/browse/HADOOP-8365
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 1.1.0
> Reporter: Eli Collins
> Priority: Blocker
>
> Per HADOOP-8230 there's a request for a flag to disable the sync code paths
> that dfs.support.append used to enable. The sync method itself will still be
> available and have a broken implementation as that was the behavior before
> HADOOP-8230. This config flag should default to false as the primary
> motivation for HADOOP-8230 is so HBase works out-of-the-box with Hadoop 1.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
