You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2022/03/29 16:00:00 UTC

[jira] [Updated] (HADOOP-18181) move org.apache.hadoop.fs.common package into hadoop-common module

     [ https://issues.apache.org/jira/browse/HADOOP-18181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran updated HADOOP-18181:
------------------------------------
    Description: 
move org.apache.hadoop.fs.common package from hadoop-aws, along with any tests, into hadoop-common jar and the+ package org.apache.hadoop.fs.impl

(except for any bits we find are broadly useful in applications to use any new APIs, in which case somewhere more public, such as  o.a.h.util.functional for the futures work)

we can and should pick on new package and move the classes there, even while they are in hadoop-aws. why so? lets us add checkstyle/findbugs rules with the final classnames

  was:
move org.apache.hadoop.fs.common package from hadoop-aws, along with any tests, into hadoop-common jar and the+ package org.apache.hadoop.fs.implel

(except for any bits we find are broadly useful in applications to use any new APIs, in which case somewhere mre public, such as  o.a.h.util.functional for the futures work)


>  move org.apache.hadoop.fs.common package into hadoop-common module
> -------------------------------------------------------------------
>
>                 Key: HADOOP-18181
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18181
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.4.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> move org.apache.hadoop.fs.common package from hadoop-aws, along with any tests, into hadoop-common jar and the+ package org.apache.hadoop.fs.impl
> (except for any bits we find are broadly useful in applications to use any new APIs, in which case somewhere more public, such as  o.a.h.util.functional for the futures work)
> we can and should pick on new package and move the classes there, even while they are in hadoop-aws. why so? lets us add checkstyle/findbugs rules with the final classnames



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org