Understanding MapR Versions

Understanding the version numbers used by MapR Core, MapR Ecosystem Packs (MEPs), MEP components, and MapR patches can help you keep your software up to date and plan for upgrades.

MapR software versions generally follow the industry-standard <major>.<minor>.<maintenance> format, with a number representing each version. However, some MapR software products use different versioning formats. The following sections describe the characteristics of the various MapR versioning formats.

MapR Core Versions

In MapR interfaces and documentation, MapR Core versions are expressed as a dot-separated string of numbers having two or three places. For example:

A change to this version . . . Typically Includes For Example
MapR Core major version Significant new features and API changes that can introduce incompatibilities with the previous version. MapR 6.x followed MapR 5.2.x and added built-in security features, MapR Database features (secondary indexes), new APIs (Apache OJAI and Change Data Capture), a new MEP series (MEP 4.x), filesystem enhancements, a new installer version, and a redesigned MapR Control System for monitoring the cluster.
MapR Core minor version New features, bug fixes, and API changes that are sometimes incompatible with the previous version. MapR 6.1 followed MapR 6.0.1 and added security by default, a new ZooKeeper version, several new MapR Database features (Node.js and Python OJAI clients, complex type support, table metrics, support for the OJAI 3.0 API), a new installer version, a new MEP series (MEP 6.x), and storage tiers for the MapR Filesystem.
MapR Core maintenance version Bug fixes only. This version typically does not introduce incompatibilities with the previous version.1 MapR 5.2.2 followed maintenance release MapR 5.2.1 and introduced new MEPs, improvements to the disk space balancer tool, and a new MapR Installer version, but did not include new features or API changes.

1MapR 6.0.1 was an exception to this rule, adding REST API access to MapR Database JSON tables, event timestamp support for stream processing, streaming audit logs for MapR-XD, and a new MEP series (MEP 5.x).

MEP Versions

In MapR interfaces and documentation, MapR Ecosystem Pack (MEP) versions are expressed as a dot-separated string of numbers having two or three places. For example:

A change to this version . . . Typically Includes For Example
MEP major version A new MEP series that supports a new major, minor, or maintenance version of MapR Core. MEP Support by MapR Core Version shows how MEP major versions change when new versions of MapR Core are introduced.
MEP minor version A significant change in features or APIs but no change in support for the current MapR Core version. MEPs 6.0.1 and 6.1.0 both support MapR 6.1.0, but MEP 6.1.0 introduced new MapR Database features, such as the C# and Go OJAI clients, as well as new features for ecosystem components (Flume, Oozie, Tez, and Apache Kafka). MEP 6.2.0, which also supports MapR 6.1.0, introduced new ecosystem component versions (Hue, Impala, Spark), updated some components (Oozie and Hive), and removed other components (Myriad and Sqoop2).
MEP maintenance version Bug fixes only. MEP maintenance versions do not add new features or API changes and are backward compatible in the same MEP series. MEPs 5.0.3, 5.0.2, and 5.0.1 added bug fixes to the MEP 5.0.x line while preserving compatibility with MapR 6.0.1.

MEP Component Versions

In MapR interfaces and documentation, MEP Component versions are expressed as a dot-separated string of numbers having two, three, or four places. For example:

For Apache Hadoop ecosystem components that have been modified for use in the MapR platform, the first two or three numerals of the version are assigned by Apache, and the MapR patch version is assigned by MapR.

A change to this version . . . Typically Includes For Example
MEP component Apache version An update to the Apache version, which can include potentially incompatible changes, new features that might be backward compatible, or bug fixes. For Apache version information, see Apache Hadoop Release Versioning.
MEP component MapR patch version An emergency bug fix (EBF) patch update, which provides bug fixes and usually does not introduce new features. See the "MEP 6.x" column of Component Versions for Released MEPs, which shows that various components in the latest MEP release include patch updates.

About the MapR Patch Version

Beginning with MEP 6.1.0, version numbers for some ecosystem components and MapR tools use a dot-separated string having four places instead of two or three places. For example:
  • Oozie 5.1.0.0
  • MapR Installer 1.11.0.0

The fourth numeral represents the MapR patch version. The MapR patch version adds a unique descriptor for patches that can occur between releases. In future releases, as new versions of components are released, more components and tools will transition to a version string that includes the MapR patch version.

How the MapR Patch Version Increments

Beginning with MEP 6.2.0, the MapR patch version can be a number in the range 0 through 999. For a newly released component, the patch version starts at 0 and increments by 1 when there is an EBF update. For example, if the MEP 6.1.0 general availability (GA) package version for Oozie is 5.1.0.0, the first bug-fix (EBF) package version will be Oozie 5.1.0.1. The next bug fix package version will be Oozie 5.1.0.2, and so on.

If the same version of a component is present in multiple MEPs, the patch version increments by 100 to provide a range of usable version numbers for future patches. This numbering scheme ensures that all patches have a unique version. The following table shows how the Oozie patch version increments for MEPs 6.1.0, 6.1.1, and 6.2.0:

MEP Oozie GA Version 1st Oozie Patch Version 2nd Oozie Patch Version
6.1.0 5.1.0.0 5.1.0.1 5.1.0.2
6.1.1 5.1.0.100 5.1.0.101 5.1.0.102
6.2.0 5.1.0.200 5.1.0.201 5.1.0.202

To obtain EBF patches, you must contact MapR Support. MapR Support makes EBF patch versions available for specific known issues. See Patches for Known Issues.

Maven Version Format

Beginning with MEP 6.2, the MapR patch version also is present in Maven artifacts for components that use the four-place versioning. In addition, the Maven version format changes to include the associated MEP instead of the YYMM timestamp:

Old Maven format with YYMM timestamp: maprdb-spark-2.2.1-mapr-1803.jar

New Maven format with MEP number: maprdb-spark-2.3.3.0-mapr-602.jar

The Maven version increments in the same way that the MapR patch version increments. This table shows how the Spark package version and Maven versions increment when new EBF patch versions become available:

MEP MEP 6.0.2 MEP 6.1.1 MEP 6.0.3* MEP 6.1.2*
Spark Package Version mapr-spark-2.3.3.0.<timestamp> mapr-spark-2.3.3.100.<timestamp> mapr-spark-2.3.3.200.<timestamp> mapr-spark-2.3.3.300.<timestamp>
Spark 1st EBF Package Version mapr-spark-2.3.3.1.<timestamp> mapr-spark-2.3.3.101.<timestamp> mapr-spark-2.3.3.201.<timestamp> mapr-spark-2.3.3.301.<timestamp>
Spark Maven Version 2.3.3.0-mapr-602 2.3.3.100-mapr-611 2.3.3.200-mapr-603 2.3.3.300-mapr-612
Spark 1st EBF Maven Version 2.3.3.1-mapr-602 2.3.3.101-mapr-611 2.3.3.201-mapr-603 2.3.3.301-mapr-612

*This release is not currently available and is included only for illustration purposes.

A patch release can trigger periodic updates to the Maven repository. You may notice patches in the sftp.mapr.com repository that are not updated in the Maven repository. This is normal. The Maven repository will be updated eventually. The latest patch versions are always propagated first to sftp.mapr.com. If you have questions about patches, contact your MapR support representative.