[EDP] Allow configuration parameters with "edp." prefix
As the EDP feature set grows, we need new configuration values for particular job types and subtypes. The additional "main_class" and "java_opts" configs for Java actions are one example of this; the mapper and reducer values for streaming MapReduce are another. Each time we add a value as a specific data field, we cause database and api changes.
We can extend the existing configuration parameter mechanism to support parameters of the form "edp.xxx". These configuration parameters will be extracted and processed by Savanna. The fundamental difference between these parameters and all others is that the others will appear in the generated workflow, but anything beginning with "edp." will not.
This mechanism will let us add any job type specific configuration parameters that we need without altering the database tables or changing the api in a way that affects clients.
Email summary here:
http://
Blueprint information
- Status:
- Complete
- Approver:
- Sergey Lukjanov
- Priority:
- Medium
- Drafter:
- Trevor McKay
- Direction:
- Approved
- Assignee:
- Trevor McKay
- Definition:
- Approved
- Series goal:
- Accepted for icehouse
- Implementation:
-
Implemented
- Milestone target:
-
2014.1
- Started by
- Trevor McKay
- Completed by
- Sergey Lukjanov
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Extract configs beginning with "savanna." from job_configs[
Addressed by: https:/
Move 'main_class' and 'java_opts' into edp.java configs
Addressed by: https:/
Update the edp user doc to discuss "edp." configs for Java jobs
Work Items
Dependency tree
* Blueprints in grey have been implemented.
