Hi Tim,
Thanks for the heads up. I could successfully build Impala 3.4.0 after
taking the relevant changes from IMPALA-9815. My previous builds seem
to have had failed due to applying both IMPALA-9815 and IMPALA-10218
patches.
The patch I ended up applying was as follows:
############################################################################
--- impala-parent/pom.xml 2020-04-10 21:55:50.000000000 +0100
+++ pom.xml.new 2020-12-03 18:26:50.195659301 +0000
@@ -143,7 +143,7 @@
</repository>
<repository>
<id>cdh.rcs.releases.repo</id>
-
<url>https://repository.cloudera.com/content/groups/cdh-releases-rcs</url>
+ <url>https://repository.cloudera.com/artifactory/cdh-releases-rcs</url>
<name>CDH Releases Repository</name>
<snapshots>
<enabled>true</enabled>
@@ -193,14 +193,6 @@
</snapshots>
</repository>
<repository>
- <id>cloudera.thirdparty.repo</id>
-
<url>https://repository.cloudera.com/content/repositories/third-party</url>
- <name>Cloudera Third Party Repository</name>
- <snapshots>
- <enabled>false</enabled>
- </snapshots>
- </repository>
- <repository>
<!--
HWX Nexus is disabled. This is a tombstone to list out why:
1. Snapshots are disabled because HWX Nexus contains snapshots
of CDH artifacts
@@ -232,9 +224,9 @@
</repositories>
<pluginRepositories>
<pluginRepository>
- <id>cloudera.thirdparty.repo</id>
-
<url>https://repository.cloudera.com/content/repositories/third-party</url>
- <name>Cloudera Third Party Repository</name>
+ <id>cdh.rcs.releases.repo</id>
+ <url>https://repository.cloudera.com/artifactory/cdh-releases-rcs</url>
+ <name>CDH Releases Repository</name>
<snapshots>
<enabled>false</enabled>
</snapshots>
############################################################################
Best Regards,
Hashan Gayasri
On Tue, Dec 8, 2020 at 10:53 PM Tim Armstrong <tarmstr...@cloudera.com> wrote:
>
> Follow-up: we're discussing a possible 3.4.1 release on the dev@impala list.
>
> On Thu, Nov 19, 2020 at 11:57 AM Tim Armstrong <tarmstr...@cloudera.com>
> wrote:
>>
>> I believe this patch fixed that issue -
>> https://gitbox.apache.org/repos/asf?p=impala.git;h=481ea4a
>>
>> On Sun, Nov 15, 2020 at 6:54 PM Hashan Gayasri <hashan.gaya...@gmail.com>
>> wrote:
>>>
>>> Hi,
>>>
>>> I tried building Impala version 3.3.0 again and got the same error. I
>>> believe that this is because of the repository location change from
>>> https://repository.cloudera.com/content/groups/* to
>>> https://repository.cloudera.com/artifactory/* . Does anyone know of a
>>> correct patch to apply for the latest Impala 3.4.0 to build or a
>>> recent working snapshot/commit of Impala?
>>>
>>> Error details:
>>> [WARNING] The POM for
>>> net.sourceforge.czt.dev:cup-maven-plugin:jar:1.6-cdh is missing, no
>>> dependency information available
>>> [INFO] BUILD FAILURE
>>> [ERROR] Plugin net.sourceforge.czt.dev:cup-maven-plugin:1.6-cdh or
>>> one of its dependencies could not be resolved: Could not find artifact
>>> net.sourceforge.czt.dev:cup-maven-plugin:jar:1.6-cdh in
>>> cloudera.thirdparty.repo
>>> (https://repository.cloudera.com/content/repositories/third-party) ->
>>> [Help 1]
>>>
>>> Thank you.
>>>
>>> Regards,
>>> Hashan Gayasri
>>>
>>> On Thu, Nov 12, 2020 at 5:04 PM Hashan Gayasri <hashan.gaya...@gmail.com>
>>> wrote:
>>> >
>>> > Hi all,
>>> >
>>> > Impala 3.4.0 Maven Repository Issues and Building With A User-Provided
>>> > Kudu Build
>>> >
>>> > While attempting to build Impala 3.4.0 release along with Kudu 1.13.0,
>>> > I got the following errors:
>>> >
>>> > [ERROR] Failed to execute goal on project
>>> > impala-minimal-hive-exec: Could not resolve dependencies for project
>>> > org.apache.impala:impala-minimal-hive-exec:jar:0.1-SNAPSHOT: Failed to
>>> > collect dependencies at
>>> > org.apache.hive:hive-exec:jar:2.1.1-cdh6.x-SNAPSHOT ->
>>> > org.cloudera.logredactor:logredactor:jar:2.0.7: Failed to read
>>> > artifact descriptor for
>>> > org.cloudera.logredactor:logredactor:jar:2.0.7: Could not transfer
>>> > artifact org.cloudera.logredactor:logredactor:pom:2.0.7 from/to
>>> > glassfish-repo-archive.repo
>>> > (https://mvnrepository.com/artifact/org.glassfish/javax.el/):
>>> > Authorization failed for
>>> > https://mvnrepository.com/artifact/org.glassfish/javax.el/org/cloudera/logredactor/logredactor/2.0.7/logredactor-2.0.7.pom
>>> > 403 Forbidden -> [Help 1]
>>> >
>>> > [ERROR] Plugin net.sourceforge.czt.dev:cup-maven-plugin:1.6-cdh or
>>> > one of its dependencies could not be resolved: Could not find artifact
>>> > net.sourceforge.czt.dev:cup-maven-plugin:jar:1.6-cdh in
>>> > cloudera.thirdparty.repo
>>> > (https://repository.cloudera.com/content/repositories/third-party) ->
>>> > [Help 1]
>>> >
>>> >
>>> >
>>> > I noticed that the https://repository.cloudera.com/content/groups/
>>> > repositories have been replaced with
>>> > https://repository.cloudera.com/artifactory/ repositories. So I
>>> > applied the following 2 patches to the impala-parent/pom.xml file
>>> > logged under the following commits as they seemed to be related to my
>>> > issue:
>>> > *
>>> > https://github.com/apache/impala/commit/04ce57dcaf338cb92ae8c811736fb99b58acc047
>>> > *
>>> > https://github.com/apache/impala/commit/481ea4ab0d476a4aa491f99c2a4e376faddc0b03
>>> > Using the following snippet.
>>> > #--------------------------------------------------------------------------------------------------
>>> > set -e
>>> > for patch in \
>>> >
>>> > "https://github.com/apache/impala/commit/04ce57dcaf338cb92ae8c811736fb99b58acc047.patch";
>>> > \
>>> >
>>> > "https://github.com/apache/impala/commit/481ea4ab0d476a4aa491f99c2a4e376faddc0b03.patch";
>>> > ;
>>> > do
>>> > PATCH_FILE=$(basename "$patch")
>>> > [[ -f "$PATCH_FILE".applied ]] && continue
>>> > wget -c -O "$PATCH_FILE" "$patch"
>>> > git apply --include=impala-parent/pom.xml "$PATCH_FILE"
>>> > touch "$PATCH_FILE".applied
>>> > done
>>> > #--------------------------------------------------------------------------------------------------
>>> >
>>> > But I'm still getting the following error:
>>> >
>>> > [ERROR] Failed to execute goal on project impala-frontend: Could
>>> > not resolve dependencies for project
>>> > org.apache.impala:impala-frontend:jar:0.1-SNAPSHOT: The following
>>> > artifacts could not be resolved:
>>> > org.apache.hadoop:hadoop-aws:jar:3.0.0-cdh6.x-SNAPSHOT, ... : Failure
>>> > to find org.apache.hadoop:hadoop-aws:jar:3.0.0-cdh6.x-SNAPSHOT in
>>> > file:///home/hashan/BUILD/impala-3.4.0/impala-3.4.0/toolchain/kudu-4ed0dbbd1/java/repository
>>> > was cached in the local repository, resolution will not be reattempted
>>> > until the update interval of impala.toolchain.kudu.repo has elapsed or
>>> > updates are forced -> [Help 1]
>>> >
>>> > I have set the env variables KUDU_CLIENT_DIR and KUDU_BUILD_DIR to
>>> > proper locations. But the toolchain kudu still seems to be used. I
>>> > have also set USE_CDH_KUDU=false .
>>> >
>>> > The same build procedure worked without any issue with Impala 3.3.0
>>> > along with Kudu 1.11.1. Kindly let me know if I should be following
>>> > any additional steps or make any other changes.
>>> > Thanks in advance for any advice on this.
>>> >
>>> > Regards,
>>> > Hashan Gayasri
>>> >
>>> > --
>>> > -Hashan Gayasri
>>>
>>>
>>>
>>> --
>>> -Hashan Gayasri
--
-Hashan Gayasri
