4 min read
We're excited today to announce the release of the MapR Ecosystem Packs process and our first MapR Ecosystem Pack (MEP). We'd like to go over how this will work and what you can expect from this process moving forward.
Each MEP contains a subset of the greater supported Hadoop ecosystem certified to work fully and completely with the other components in each release. This allows us to provide more nuanced support like bundling Spark JARs into Oozie, for example.
We find that this picture is useful for understanding what subset of ecosystem projects we're including in this:
Each MapR Core release will be supported by multiple MEPs, giving you multiple opportunities for upgrade.
For more information, please see the Whiteboard Walkthrough here:
For a list of what each MEP contains, please go here.
MapR Ecosystem Packs (MEPs) will be installed and upgraded through the new installer that is releasing with MapR 5.2. For installation and upgrade directions, please visit our documentation here.
MEP is on a quarterly release schedule, meaning that a new major MEP release will normally come out every three months, starting in August with MEP 1.0.
When the next MapR release occurs.
The rationale for this is that early in a release cycle, we are providing many opportunities to upgrade. Later in the cycle, as customers are moving into production, there is less demand for upgrades that could be disruptive. This allows us to offer both flexibility and stability.
Bug fix versions will continue to be offered on each project in each supported MEP, until the MapR release hits EOL.
In order to get on the MEP "path," an upgrade to MapR 5.2 will be required. We will not be supporting MapR versions prior to MapR 5.2. These versions will continue to receive bug fix and patch releases.
Partners will certify on MapR+MEP combinations. Since not every MEP will have an upgrade for each project, many certifications can be grandfathered in.
Stay ahead of the bleeding edge...get the best of Big Data in your inbox.