The GitHub Actions job "Docs 404 check (beta)" on flink.git/flink-40627 has 
failed.
Run started by GitHub user dalelane (triggered by dalelane).

Head commit for run:
6ac36de606f6dec6023fd26560beec575c5949ed / Dale Lane <[email protected]>
[FLINK-40627][clients] Separate artifacts fetched from different URIs

Fetched artifacts are cached in user.artifacts.base-dir based on
filename. There are times where this could result in unexpected
and undesired behaviour:

- Redeploys where user.artifacts.base-dir is in persistent storage
  Changing the job ...artifactstore/app.jar?v=1 to
  ...artifactstore/app.jar?v=2 will reuse the v1 jar and never
  fetch the v2 jar
- Standalone clusters that share a base-dir, where one job wants
  somehost/app.jar and another job wants differenthost/app.jar
  could inadvertently both run the first jar to be fetched
- Multiple artifacts with the same file name, such as a job that
  uses s3://bucket-one/udf.jar and s3://bucket-two/udf.jar could
  reuse the first jar to be fetched for both
- Jars that are uniquely identified by query parameters, such as
  an artifact store that has .../download?id=X and
  .../download?id=Y to identify unrelated jars, but where every
  URI has a common last path segment such as "download"

Artifacts are now stored in a subdirectory of
user.artifacts.base-dir, with the subdirectory given a name from a
hash of it's full source URI, including any query parameters.

Artifact fetch manager tests confirm the behaviour.

Signed-off-by: Dale Lane <[email protected]>

Report URL: https://github.com/apache/flink/actions/runs/37026810300

With regards,
GitHub Actions via GitBox

Reply via email to