Laszlo Gaal created IMPALA-14972:
------------------------------------
Summary: Start using Maven Remote Repo Filters for dependency
resolution
Key: IMPALA-14972
URL: https://issues.apache.org/jira/browse/IMPALA-14972
Project: IMPALA
Issue Type: Improvement
Components: Infrastructure
Affects Versions: Impala 5.0.0
Reporter: Laszlo Gaal
Impala builds have recently run into Maven dependency resolution problems
where remote Maven repositories banned/rejected requests coming from the public
Jenkins instance, or various other downstream build automation facilities.
Most of these bans could be traced back to dependency lookup requests not being
specific enough, i.e. repeatedly asking a repo for dependencies not hosted
there. The Apache repository (repository.apache.org), Shibboleth's public repo
(build.shibboleth.net/maven) and probably others have hit count or hit rate
limits that Maven can trigger, as its default search algorithm is not too
sophisticated: when looking for an artifact, it will query every remote repo it
knows, until the artifact is found.
Maven 3.9 introduced Remote Repository Filters to curtail this behavior: remote
artifact repos can now supply prefix strings stating what artifacts (or
artifact groups) they can supply; see
[https://maven.apache.org/resolver/remote-repository-filtering.html]
Impala should start using this mechanism to reduce dependency resolution
traffic and time, and to avoid triggering bans.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
