Re: AMATERASU-44

Hi Arun, AMATERASU-44 and its python version AMATERASU-46 (which I believe @nadav started working on) are about moving away from the implicit persistence mechanism in the current Amaterasu implementation. The base for those changes is the existence of a datastores.yaml file in the container which

[jira] [Commented] (AMATERASU-49) Generate env.yml per container

[ https://issues.apache.org/jira/browse/AMATERASU-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16645992#comment-16645992 ] Yaniv Rodenski commented on AMATERASU-49: - After a discussion, we have decided

[jira] [Updated] (AMATERASU-44) Spark Scala - Move the persistence functionality from the runner implementation into AmaContext

[ https://issues.apache.org/jira/browse/AMATERASU-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Rodenski updated AMATERASU-44: Issue Type: Improvement (was: Task) > Spark Scala - Move the persistence functionality f

AMATERASU-44

Hi Yaniv and all, I am trying to take a stab at AMATERASU-44 and would like to get some background behind this issue - specifically around the current state and what are the things that ought to be considered before making the change. Cheers, A

[jira] [Resolved] (AMATERASU-28) Pull Miniconda version away from compiled code

[ https://issues.apache.org/jira/browse/AMATERASU-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Manivannan resolved AMATERASU-28. -- Resolution: Fixed Assignee: Yaniv Rodenski (was: Arun Manivannan) > Pull Minic

[jira] [Commented] (AMATERASU-28) Pull Miniconda version away from compiled code

[ https://issues.apache.org/jira/browse/AMATERASU-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16645834#comment-16645834 ] Arun Manivannan commented on AMATERASU-28: -- This issue is already fixed as par