Versioning

Last Updated: Jun 22, 2017

  • E-MapReduce applies a version number rule in the a.b.c format:

    a indicates major changes to the version. b indicates moderate changes to some components in the version. c indicates bug fixes in the version and can be compatible with previous versions. For example, the update from 1.0.0 to 2.0.0 is a major version change. After a version upgrade, we recommend that you test to ensure all previous jobs can run normally. An update from 1.0.0 and 1.1.0 is a change generally conducted to upgrade a component version. We recommend that you perform a similar test to verify jobs run normally. An update from 1.0.0 and 1.0.1 is a c position change, and remains fully compatible with previous versions.

  • The software and version bound on each E-MapReduce are fixed. E-MapReduce does not support selection from multiple different versions of software, and manual changes to the version of the software is not recommended.

  • If a release version of E-MapReduce is selected, and is then created on the cluster, the version used by the cluster will not upgrade automatically. The images corresponding to the subsequent version will not affect the cluster created after upgrade as only new clusters use the new images.

  • When you upgrade the version of the cluster (for example, from 1.0.x to 1.1.x), we recommend that you test your jobs to ensure that they run normally in the new software environment.

For details about the version of E-MapReduce, refer to Product Version Update Record.

Thank you! We've received your feedback.