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

   ## What is the purpose of the change
   
   This pull request make HistoryServer support application archives while 
ensuring that legacy job archives are handled properly.
   
   
   ## Brief change log
   
   - Add configuration options for application archive fetching
   - Adapt the archive retention strategy to be compatible with application 
archives
   - Introduce a new archiveFetcher for application archives (and their 
associated job archives)
   - Integrate the new archiveFetcher into the HistoryServer
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
   - Updated tests for archive retention strategy to include coverage for 
application archives
   - Added tests that validates the behavior of the HistoryServer when fetching 
jobs and applications
   - Manually verified the change by running a standalone cluster and 
HistoryServer, confirming that the archives can be parsed properly and served 
via REST responses
   
   
   ## 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: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes)
     - If yes, how is the feature documented? (docs)
   


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