Hi Flink team,
When I tried to build flink 1.10 source code, I always got the following build error:
[ERROR] Failed to execute goal on project flink-connector-hive_2.11: Could not resolve dependencies for project org.apache.flink:flink-connector-hive_2.11:jar:1.10.0: Failed to collect
dependencies at org.apache.hive.hcatalog:hive-webhcat-java-client:jar:1.1.0 -> org.apache.hive.hcatalog:hive-hcatalog-core:jar:1.1.0 -> org.apache.hive:hive-cli:jar:1.1.0 -> org.apache.hive:hive-service:jar:1.1.0 -> org.apache.hive:hive-exec:jar:1.1.0 -> org.apache.calcite:calcite-core:jar:1.0.0-incubating
-> org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde: Failed to read artifact descriptor for org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde: Could not transfer artifact org.pentaho:pentaho-aggdesigner-algorithm:pom:5.1.5-jhyde from/to mapr-releases
(https://repository.mapr.com/maven/): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :flink-connector-hive_2.11
And this is my build command:
mvn install -DskipTests -Dhadoop.version=2.6.0-cdh5.7.3 -Pinclude-hadoop -Pvendor-repos -Pscala-2.11 -Pfast -Djavax.net.debug=SSL -Phive-1.1.0 -Pskip-hive-tests -Dsun.security.ssl.allowUnsafeRenegotiation=true
Could anyone know how to resolve it?
Thanks,
Russell
|
MapR has a known problem with their
HTTPS repository where certificates are being rejected in some
(not well-defined) cases.
The only reliable workaround is to work
against the HTTP repository.
Do also note that the vendor-repos
profile no longer exists in 1.10; additional repositories must be
configured in your own maven setup.
On 20/02/2020 12:29, Russell Bie wrote:
|
Free forum by Nabble | Edit this page |