[
https://issues.apache.org/jira/browse/HADOOP-18181?focusedWorklogId=797344&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-797344
]
ASF GitHub Bot logged work on HADOOP-18181:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 02/Aug/22 18:37
Start Date: 02/Aug/22 18:37
Worklog Time Spent: 10m
Work Description: steveloughran opened a new pull request, #4676:
URL: https://github.com/apache/hadoop/pull/4676
### Description of PR
extra changes on top of #4673
* moves the common classes to the impl.prefetch package in hadoop common
* production code review; remove this. refs out of all but ctor
* test code, directly move to intercept
not done: javadocing comments, reduce logging
### How was this patch tested?
in progress against s3 london
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [.] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
Issue Time Tracking
-------------------
Worklog Id: (was: 797344)
Remaining Estimate: 0h
Time Spent: 10m
> 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
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
