[
https://issues.apache.org/jira/browse/HDFS-12882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277157#comment-16277157
]
Chris Douglas commented on HDFS-12882:
--------------------------------------
bq. My only concern is changing getFileInfo(String src) into getFileInfo(String
src, boolean needLocation) for ClientProtocol. How incompatible is this?
{{ClientProtocol}} is private/evolving, so this should be safe. Clients writing
against {{FileSystem}}/{{DistributedFileSystem}} shouldn't notice. Because it's
private/evolving, I thought changing all the occurrences was preferable to an
overload. Old clients implicitly get the correct semantics from new servers
because {{needLocation}} defaults to false. New clients talking to old servers
will get errors because the location field was ignored. We might be able to
improve the error message, here.
As an aside, this should make it possible to implement
{{DistributedFileSystem::getLocatedFileStatus}}. This would make it easier for
globbing to consistently query with locations, avoiding some RPCs
(MAPREDUCE-7016).
bq. What about other projects like MapReduce, any breaks there?
There shouldn't be, since all the existing calls should pass through the
existing code. I'll run the unit tests.
> Support full open(PathHandle) contract in HDFS
> ----------------------------------------------
>
> Key: HDFS-12882
> URL: https://issues.apache.org/jira/browse/HDFS-12882
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs-client
> Reporter: Chris Douglas
> Assignee: Chris Douglas
> Attachments: HDFS-12882.00.patch, HDFS-12882.00.salient.txt
>
>
> HDFS-7878 added support for {{open(PathHandle)}}, but it only partially
> implemented the semantics specified in the contract (i.e., open-by-inodeID).
> HDFS should implement all permutations of the default options for
> {{PathHandle}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
