[ 
https://issues.apache.org/jira/browse/IMPALA-10002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fang-Yu Rao updated IMPALA-10002:
---------------------------------
    Description: 
We have seen the following error in a recent Impala build.
{code:java}
16:21:48 [ERROR] Failed to execute goal on project impala-frontend: Could not 
resolve dependencies for project 
org.apache.impala:impala-frontend:jar:0.1-SNAPSHOT: Could not transfer artifact 
org.apache.ranger:ranger-plugin-classloader:jar:2.0.0.7.2.1.0-287 from/to 
impala.cdp.repo 
(https://native-toolchain.s3.amazonaws.com/build/cdp_components/4493826/maven): 
Connection to https://native-toolchain.s3.amazonaws.com refused: Connection 
timed out (Connection timed out) -> [Help 1]
{code}

The error message is very similar to that reported in IMPALA-9928, which has 
been closed already. We thus create a new JIRA to keep track of the issue. 
Maybe [~laszlog] could also provide some insight into this. Thanks!

> Build failure due to unresolved dependencies
> --------------------------------------------
>
>                 Key: IMPALA-10002
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10002
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Infrastructure
>            Reporter: Fang-Yu Rao
>            Assignee: Laszlo Gaal
>            Priority: Major
>              Labels: broken-build
>
> We have seen the following error in a recent Impala build.
> {code:java}
> 16:21:48 [ERROR] Failed to execute goal on project impala-frontend: Could not 
> resolve dependencies for project 
> org.apache.impala:impala-frontend:jar:0.1-SNAPSHOT: Could not transfer 
> artifact org.apache.ranger:ranger-plugin-classloader:jar:2.0.0.7.2.1.0-287 
> from/to impala.cdp.repo 
> (https://native-toolchain.s3.amazonaws.com/build/cdp_components/4493826/maven):
>  Connection to https://native-toolchain.s3.amazonaws.com refused: Connection 
> timed out (Connection timed out) -> [Help 1]
> {code}
> The error message is very similar to that reported in IMPALA-9928, which has 
> been closed already. We thus create a new JIRA to keep track of the issue. 
> Maybe [~laszlog] could also provide some insight into this. Thanks!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to