Mailing-List: contact user-help@bigtop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@bigtop.apache.org
MIME-Version: 1.0
Date: Sun, 3 Apr 2016 23:07:12 -0700
Message-ID: 
 <CAGtDTYAFJoOQUKAaNgdc9VcmY4WFLktavg528XTG-+i8QVLNGg@mail.gmail.com>
Subject: Bigtop Multiple Versions
From: Kyle B <kbinaz@gmail.com>
To: user@bigtop.apache.org
Content-Type: multipart/alternative; boundary=001a114026d62b7a27052fa28ad5

--001a114026d62b7a27052fa28ad5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello,

I=E2=80=99m new to Bigtop, just starting to incorporate it into where I wor=
k, and
had a general question. Is there a recommended way for managing multiple
versions of the same package in Bigtop? As an example, I=E2=80=99d like to =
use
Bigtop to manage multiple builds of Spark (1.3, 1.4, 1.5, 1.6).

I tried updating the BOM to have multiple Spark definitions, and ran into
some issues doing that. As each version could potentially require custom
patches, I don=E2=80=99t want to have just one spark and update the version=
 number
during the build.

I=E2=80=99ve thought about creating different branches for each version of =
Spark,
and applying the appropriate patches in each branch, but I=E2=80=99m wonder=
ing if
there=E2=80=99s a better way?

This isn=E2=80=99t specific to Spark. We=E2=80=99re currently in the proces=
s of upgrading
our Hadoop cluster from 2.2 to 2.7, and wanted to have two different
versions of Hadoop I could toggle back and forth between.

So I guess my question is, is there an easy way for managing different
versions of the same package in Bigtop without going down the git branches
road? Any advice you can offer for best ways to do this is much appreciated=
.

Thanks,

-Kyle

--001a114026d62b7a27052fa28ad5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">


<p class=3D"">Hello,</p>
<p class=3D"">I=E2=80=99m new to Bigtop, just starting to incorporate it in=
to where I work, and had a general question. Is there a recommended way for=
 managing multiple versions of the same package in Bigtop? As an example, I=
=E2=80=99d like to use Bigtop to manage multiple builds of Spark (1.3, 1.4,=
 1.5, 1.6).</p>
<p class=3D"">I tried updating the BOM to have multiple Spark definitions, =
and ran into some issues doing that. As each version could potentially requ=
ire custom patches, I don=E2=80=99t want to have just one spark and update =
the version number during the build.</p>
<p class=3D"">I=E2=80=99ve thought about creating different branches for ea=
ch version of Spark, and applying the appropriate patches in each branch, b=
ut I=E2=80=99m wondering if there=E2=80=99s a better way?</p>
<p class=3D"">This isn=E2=80=99t specific to Spark. We=E2=80=99re currently=
 in the process of upgrading our Hadoop cluster from 2.2 to 2.7, and wanted=
 to have two different versions of Hadoop I could toggle back and forth bet=
ween.</p>
<p class=3D"">So I guess my question is, is there an easy way for managing =
different versions of the same package in Bigtop without going down the git=
 branches road? Any advice you can offer for best ways to do this is much a=
ppreciated.</p>
<p class=3D"">Thanks,</p>
<p class=3D"">-Kyle</p></div>

--001a114026d62b7a27052fa28ad5--