dmvk edited a comment on pull request #18059:
URL: https://github.com/apache/flink/pull/18059#issuecomment-993245732


   There are still places in CI scripts where the version needs to be bumped:
   - There is another entry in `azure-pipelines.yml`
   - Multiple entries in `build-apache-repo.yml` [1]  (cron  jobs)
   
   > I think the CI work is enough to ensure that 2.8.5 is compatibility, am I 
right?
   
   Yes... but. Purpose of this JIRA /  PR is to upgrade a minimal compile-time 
version of hadoop. We still have CRON that runs against `2.4.1` [2] -> the 
lower bound for the compile-time compatibility is still `2.4.1`, which means 
this change doesn't provide a desired outcome.
   
   To overcome this limitation we only need to change the **runtime version** 
of Hadoop in CI scripts (instead of both compile & runtime  versions).
   
   To simulate this locally, simply try using some of the classes (eg. the 
CallerContext) that are only available in 2.8.x  in hadoop-fs module, and then 
test it with:
   
   ```
   mvn install -pl flink-filesystems/flink-hadoop-fs -Dhadoop.version=2.4.1
   ``` 
   
   [1] 
https://github.com/apache/flink/blob/release-1.14.0/tools/azure-pipelines/build-apache-repo.yml
   [2] 
https://github.com/apache/flink/blob/release-1.14.0/tools/azure-pipelines/build-apache-repo.yml#L123


-- 
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: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to