Nadav Har Tzvi created AMATERASU-27:
---------------------------------------
Summary: ama CLI doesn't take into account amaterasu.properties
changes in YARN
Key: AMATERASU-27
URL: https://issues.apache.org/jira/browse/AMATERASU-27
Project: AMATERASU
Issue Type: Bug
Affects Versions: 0.2.1-incubating
Environment: any hadoop cluster
Reporter: Nadav Har Tzvi
Assignee: Nadav Har Tzvi
Fix For: 0.2.1-incubating
To reproduce:
# On a hadoop cluster
# Setup Amaterasu
# Run a job
# Run ama setup again and change something
# Run a job. The changed setting will not be taken into account.
How to fix:
We need an indication that amaterasu.properties has changed, it can be any
mechanism
(boolean flag, keep record of last 2 file hashes, etc)
When we execute {{ama run}} then the CLI should check whether or not there is a
new version of amaterasu.properties. If there is a new version, upload it to
HDFS.
Existing workarounds:
executing {{ama run}} with {{--force-bin}} will completely remove the existing
Amaterasu HDFS assets and will upload everything again. While it is not amazing
and consumes tons of time (has to upload the Spark client again), it works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
