+1
On 6. July 2018 at 18:50:37, Davor Bonaci (da...@apache.org) wrote:
+1
"have been released" --> "have been built and voted upon"
On Fri, Jul 6, 2018 at 12:51 AM, Yaniv Rodenski wrote:
> Hi All,
>
> Sorry for doing this late again, but I propose the following report to be
> submitted:
>
>
+1
On 24. June 2018 at 12:00:12, Arun Manivannan (a...@arunma.com) wrote:
Clean built. Testcases run fine. Ran it on HDP and HDP 2.6.5.0-292 with
minor change on the leader AM. Works perfect.
+1
Cheers,
Arun
On Sun, Jun 24, 2018 at 5:10 PM guy peleg wrote:
> Downloaded the source code
[
https://issues.apache.org/jira/browse/AMATERASU-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eyal Ben Ivri updated AMATERASU-22:
---
Description:
Currently, YARN containers are created without consideration for specific
[
https://issues.apache.org/jira/browse/AMATERASU-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eyal Ben Ivri reassigned AMATERASU-6:
-
Assignee: Eyal Ben Ivri
> Long running actions/pipeli
Eyal Ben Ivri created AMATERASU-22:
--
Summary: Improve the way yarn containers are allocated to consider
specific task requirments
Key: AMATERASU-22
URL: https://issues.apache.org/jira/browse/AMATERASU-22
[
https://issues.apache.org/jira/browse/AMATERASU-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eyal Ben Ivri resolved AMATERASU-18.
Resolution: Fixed
> Containers are not influenced by framework configurat
Hi to all,
Sorry for not replying sooner, but I have been following the thread closely.
It is quite obvious we need to find more people that will be active in the
Amaterasu project.
Yaniv and myself are often communicating through private channels (and I
believe other developers are doing the
