[jira] [Assigned] (BEAM-3621) HCatalog failing frequently on fetch of org.pentaho:pentaho-aggdesigner-algorithm:5.1.5-jhyde

2018-03-07 Thread Luke Cwik (JIRA)

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

Luke Cwik reassigned BEAM-3621:
---

Assignee: Alan Myrvold

> HCatalog failing frequently on fetch of 
> org.pentaho:pentaho-aggdesigner-algorithm:5.1.5-jhyde
> -
>
> Key: BEAM-3621
> URL: https://issues.apache.org/jira/browse/BEAM-3621
> Project: Beam
>  Issue Type: Bug
>  Components: io-java-hcatalog
>Reporter: Kenneth Knowles
>Assignee: Alan Myrvold
>Priority: Critical
>  Labels: flake
> Fix For: Not applicable
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The download seems to fail. There are three aspects to this:
>  - The Gradle build should have a local persistent cache so it isn't 
> fetching. But as I understand it Gradle has a policy of still pinging the 
> repo even when cached.
>  - The Gradle build is probably re-fetching due to {{--rerun-tasks}} so we 
> need to stop doing that.
>  - The artifact is not in "Central" repository but in "Spring Plugins". That 
> is probably why all the failures are on this artifact and no other artifacts 
> cause failures.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (BEAM-3621) HCatalog failing frequently on fetch of org.pentaho:pentaho-aggdesigner-algorithm:5.1.5-jhyde

2018-02-14 Thread Kenneth Knowles (JIRA)

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

Kenneth Knowles reassigned BEAM-3621:
-

Assignee: (was: Reuven Lax)

> HCatalog failing frequently on fetch of 
> org.pentaho:pentaho-aggdesigner-algorithm:5.1.5-jhyde
> -
>
> Key: BEAM-3621
> URL: https://issues.apache.org/jira/browse/BEAM-3621
> Project: Beam
>  Issue Type: Bug
>  Components: io-java-hcatalog
>Reporter: Kenneth Knowles
>Priority: Critical
>  Labels: flake
>
> The download seems to fail. There are three aspects to this:
>  - The Gradle build should have a local persistent cache so it isn't 
> fetching. But as I understand it Gradle has a policy of still pinging the 
> repo even when cached.
>  - The Gradle build is probably re-fetching due to {{--rerun-tasks}} so we 
> need to stop doing that.
>  - The artifact is not in "Central" repository but in "Spring Plugins". That 
> is probably why all the failures are on this artifact and no other artifacts 
> cause failures.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)