mohsenrezaeithe opened a new pull request, #26944:
URL: https://github.com/apache/flink/pull/26944

   ## What is the purpose of the change
   
   This change introduces new Maven modules under the `flink-filesystems` 
module for updating Hadoop FileSystem dependencies for the corresponding 
extensions. The new Hadoop 3.4 module introduces a new pattern that allows the 
extensions to pick the version that best suit the standards for their logic.
   
   Some dependencies have also been refactored to the higher file system 
modules to reduce dependency management across the modules within 
`org.apache.flink:flink-filesystems`.
   
   ## Brief change log
   
   - Refactored archunit tests dependencies to the `flink-filesystem` module.
   - Moved the `provided` `org.apache.flink:flink-core` dependency to the 
`flink-filesystem` module.
   - Migrated Hadoop 3.3/AWS modules to a new 3.3 parent under 
`flink-filesystems` module.
   - Implemented a new Hadoop 3.4 module, and migrated `flink-azure-fs-hadoop` 
to use it.
   
   ## Verifying this change
   
   This is a dependency refactor and the current `flink-filesystem` module 
tests already cover its tests.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): **yes**
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: **no**
     - The serializers: **no**
     - The runtime per-record code paths (performance sensitive): **no**
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: **no**
     - The S3 file system connector: **no** (its dependencies where cleaned up, 
but none of them had a version change)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? **no**
     - If yes, how is the feature documented? **not applicable**
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to