[
https://issues.apache.org/jira/browse/HADOOP-13502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HADOOP-13502:
-----------------------------------
Attachment: HADOOP-13502-branch-2.002.patch
Steve and I spoke offline. I had a misunderstanding about his last comment.
His point was that we really don't have any other known object stores. There
are other file system implementations, but as far as we know, they are not
object stores, and therefore they would never set the is-blobstore flag.
Based on that, I'm uploading patch 002. This retains is-blobstore as an
informational flag. It is not deprecated. The tests no longer need to check
for is-blobstore, because all known object stores have had their contract XML
options updated. As a side effect, the patch no longer needs to touch wasb.xml.
> Rename/split fs.contract.is-blobstore flag used by contract tests.
> ------------------------------------------------------------------
>
> Key: HADOOP-13502
> URL: https://issues.apache.org/jira/browse/HADOOP-13502
> Project: Hadoop Common
> Issue Type: Improvement
> Components: test
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Priority: Minor
> Attachments: HADOOP-13502-branch-2.001.patch,
> HADOOP-13502-branch-2.002.patch
>
>
> The {{fs.contract.is-blobstore}} flag guards against execution of several
> contract tests to account for known limitations with blob stores. However,
> the name is not entirely accurate, because it's still possible that a file
> system implemented against a blob store could pass those tests, depending on
> whether or not the implementation matches the semantics of HDFS. This issue
> proposes to rename the flag or split it into different flags with different
> definitions for the semantics covered by the current flag.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
