ferenc-csaky opened a new pull request, #24065:
URL: https://github.com/apache/flink/pull/24065
## What is the purpose of the change
Support fetching remote job JAR and additional artifacts (UDFs, formats,
dependencies, etc.) in nativa Kubernetes and standalone application mode. The
current change contains fetchers for DFS (via Flink FS abstraction) and HTTP.
## Brief change log
* In standalone app mode, a `--jars` option is added, which has unlimited
args, which will be fetched before the Flink cluster start. Example:
```sh
./bin/standalone-job.sh start-foreground \
--jars http://localhost:9999/flink-sandbox.jar
http://localhost:9999/test-udf.jar \
--job-classname org.apache.flink.DummyJob
```
* In native K8s app mode, the user can define additional artifacts via the
`user.artifacts.artifact-list` property. Example:
```sh
./bin/flink run-application \
--target kubernetes-application \
-Dkubernetes.cluster-id=flink-cluster \
-Dkubernetes.container.image.ref=flink \
-Duser.artifacts.artifact-list=http://host.minikube.internal:9999/test-udf.jar \
http://host.minikube.internal:9999/flink-sandbox.jar
```
## Verifying this change
This change added tests and can be verified as follows:
* Added tests for artifact fetching utils.
* Added tests for artifact fetching logic.
* Added tests to cover the changes in `DefaultPackagedProgramRetriever`.
## 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: Artifact deployment in
native Kubernetes app mode.
- 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: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
