Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Ambari release versioning

avatar
Super Guru

Hi,

Can somebody explain about Ambari version naming standard?

Looking similar to HDP https://community.hortonworks.com/questions/41422/question-on-hdp-versioning.html

1 ACCEPTED SOLUTION

avatar
Super Guru

Thanks @Mats Johansson so as per doc (<major>.<minor>.<maintenance> ) if I'm using Ambari 2.2.1 and want to upgrade to 2.2.2 then that will be a maintenance release upgrade with no new feature addition, right?.

View solution in original post

6 REPLIES 6

avatar
Super Collaborator

Hi @Jitendra,

Please have a look at http://hadoop.apache.org/versioning.html - It cover Ambari as well.

/Best regards, Mats

avatar
Super Guru

Thanks @Mats Johansson so as per doc (<major>.<minor>.<maintenance> ) if I'm using Ambari 2.2.1 and want to upgrade to 2.2.2 then that will be a maintenance release upgrade with no new feature addition, right?.

avatar
Super Guru

@Jitendra Yadav

Correct. That is a maintenance release dealing with bugs associated with features that already part of the release.

avatar
Super Guru

Thanks @Constantin Stanca But wondering why Ambari 2.2.2 has new feature (Grafana) even it was a maintainence release.

avatar
Super Guru

@Jitendra Yadav

Good question. It shouldn't. Occasionally, a feature may slip in. As long as it is not a major change, it is probably something tolerated. It could be also a Tech Preview which is probably the case with Grafana and that is probably fine. Did that feature break an existent functionality?

avatar
Guru

Correct, if the change is non-destructive, it will be considered for a maint. release. But I should point out that the community tries to minimize this though. Cheers.