[
https://issues.apache.org/jira/browse/HADOOP-13321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15349837#comment-15349837
]
Chris Nauroth commented on HADOOP-13321:
----------------------------------------
bq. I support this...though it'd need to be backed by an audit of downstream
projects (hive, spark, hbase) to make sure they are moved on too
I think Hive and Pig are all set after I gave them a few patches a while ago,
unless they added new code that called these methods. I also have this under
way for Tez, ORC and Spark. I haven't looked at HBase yet, but I can add it to
the list.
> Deprecate FileSystem APIs that promote inefficient call patterns.
> -----------------------------------------------------------------
>
> Key: HADOOP-13321
> URL: https://issues.apache.org/jira/browse/HADOOP-13321
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
> Reporter: Chris Nauroth
> Assignee: Mingliang Liu
>
> {{FileSystem}} contains several methods that act as convenience wrappers over
> calling {{getFileStatus}} and retrieving a single property of the returned
> {{FileStatus}}. These methods have a habit of fostering inefficient call
> patterns in applications, resulting in multiple redundant {{getFileStatus}}
> calls. For HDFS, this translates into wasteful NameNode RPC traffic. For
> file systems backed by cloud object stores, this translates into wasteful
> HTTP traffic. This issue proposes to deprecate these methods and instead
> encourage applications to call {{getFileStatus}} and then reuse the same
> {{FileStatus}} instance as needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
