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

   ## What is the purpose of the change
   
   package the Native S3 FileSystem module into Flink's distribution assembly, 
making it available for users without requiring manual JAR placement. This 
completes the integration of the native S3 filesystem implementation into the 
Flink ecosystem by ensuring it is included in official distribution builds.
   
   ## Brief change log
   
   - Added native S3 FileSystem JAR 
(`flink-s3-fs-native-${project.version}.jar`) to the distribution assembly 
configuration
   - The JAR is packaged in the `opt/` directory alongside other optional 
filesystem plugins
   
   ## Verifying this change
   
   build and check the flink-dist 
   
   <img width="1227" height="682" alt="Screenshot 2026-03-19 at 4 18 37 PM" 
src="https://github.com/user-attachments/assets/3f0116e8-c14f-4c73-9f9c-3f7f8f9a35dd";
 />
   
   
   
   ## Does this pull request potentially affect one of the following parts:
   
   - Dependencies (does it add or upgrade a dependency): **no**
   - 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: **yes** - includes native S3 filesystem in 
distribution
   
   ## Documentation
   
   - Does this pull request introduce a new feature? **no**
   - If yes, how is the feature documented? **not applicable** - documentation 
for the native S3 filesystem was provided separately
   
   ## Additional Context
   
   N/A


-- 
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