Matt,
thanks, I'm agree with hadoop_version to version transition in v2 api.
On Tue, Feb 18, 2014 at 5:02 AM, Matthew Farrellee m...@redhat.com wrote:
ok, i spent a little time looking at what the change impacts and it looks
like all the template validations we have currently require
$ savanna plugins-list
+-+--+---+
| name| versions | title |
+-+--+---+
| vanilla | 1.2.1| Vanilla Apache Hadoop |
| hdp | 1.3.2| Hortonworks Data Platform |
IDH uses version of IDH distro and there is no direct mapping between
distro version and hadoop version. E.g. IDH 2.5.1 works with apache hadoop
1.0.3.
I suggest to call the field as just 'version' everywhere and assume this
version as plugin specific property.
Andrew.
On Mon, Feb 17, 2014 at
Andrew +1
The HDP plugin also returns the HDP distro version. The version needs to
make sense in the context of the plugin.
Also, many plugins including the HDP plugin will support deployment of
several hadoop versions.
-John
On Mon, Feb 17, 2014 at 2:36 PM, Andrew Lazarev
Agree to rename this legacy field to ‘version’. Adding to John's words about
HDP, Vanilla plugin is able to run different hadoop versions by doing some
manipulations with DIB scripts :-) So the right name of this field should be
‘version’ as version of engine of concrete plugin.
Regards,
ok, i spent a little time looking at what the change impacts and it
looks like all the template validations we have currently require
hadoop_version. additionally, the client uses the name and documentation
references it.
due to the large number of changes and the difficulty in providing
