So I compiled the 2.5 fgs against 2.6 when I was testing.  If we abstract
this right it may just be an if statement or two.
On Aug 7, 2015 6:47 PM, "Santosh Marella" <smare...@maprtech.com> wrote:

> > Myriad code base compiled against hadoop 2.7 should work on hadoop 2.5
> > cluster as long as FGS (i.e. zero profile NM) is not used.
>
> Verified the above. As long as FGS (zero profile NM) is not used,
> Myriad compiled against hadoop 2.7 will work on hadoop 2.5.
>
> Thanks,
> Santosh
>
> On Fri, Aug 7, 2015 at 2:20 PM, Santosh Marella <smare...@maprtech.com>
> wrote:
>
> > > It will make working on HA easier
> > Oh Yes!
> >
> > > how do we facilitate that? Profiles?
> > Profiles might be one way. Currently, FGS is supported for "zero" profile
> > only.
> > And we have seen there was an API incompatibility from 2.5 to 2.6+ in FGS
> > code.
> > So, ideally (since I haven't tried it myself), when FGS is merged into
> > phase1,
> > the Myriad code base compiled against hadoop 2.7 should work on hadoop
> 2.5
> > cluster as long as FGS (i.e. zero profile NM) is not used. (I'll try this
> > out and
> > post back what I find)
> >
> > However, in the long term we need a mechanism to abstract out the APIs
> > that are incompatible across versions.
> >
> > Thanks,
> > Santosh
> >
> > On Fri, Aug 7, 2015 at 12:12 PM, Darin Johnson <dbjohnson1...@gmail.com>
> > wrote:
> >
> >> It will make working on HA easier.  However, one concern that's been
> >> addressed previously is that FGS works for Hadoop 2.6.0+. Do we plan to
> >> support 2.5.X (anything lower?) also as Santosh has a way to do that, if
> >> so
> >> how do we facilitate that? Profiles?
> >>
> >> Darin
> >>
> >> On Fri, Aug 7, 2015 at 1:46 PM, Santosh Marella <smare...@maprtech.com>
> >> wrote:
> >>
> >> > Hello guys,
> >> >
> >> > I propose merging FGS into phase1. As I said before, I think it's at a
> >> > point where the functionality works reasonably well.
> >> > Any future improvements/fixes/UI changes can be done via separate
> JIRAs.
> >> >
> >> > Unless there are any major concerns, I'd like to merge FGS into phase1
> >> *EOD
> >> > Monday* (PDT).
> >> >
> >> > Thanks,
> >> > Santosh
> >> >
> >> > On Wed, Aug 5, 2015 at 8:16 PM, Santosh Marella <
> smare...@maprtech.com>
> >> > wrote:
> >> >
> >> > > I feel FGS is very close to making it into 0.1. PR 116 addresses
> >> moving
> >> > to
> >> > > hadoop 2.7 and making FGS and CGS coexist. This PR was recently
> >> reviewed
> >> > by
> >> > > Yulia and Darin. Darin had also tried out FGS on hadoop 2.6.x and
> >> 2.7.x
> >> > > clusters and it seemed to have worked as expected. Unless there are
> >> more
> >> > > reviews/feedback, it can be merged into issue_14. Once PR 116 is
> >> merged
> >> > > into issue_14, issue_14 can be merged into phase1.
> >> > >
> >> > > Thanks,
> >> > > Santosh
> >> > >
> >> > > On Tue, Aug 4, 2015 at 4:54 PM, Adam Bordelon <a...@mesosphere.io>
> >> > wrote:
> >> > >
> >> > >> We do have a JIRA 0.1.0 "fix version" field, but none of our issues
> >> use
> >> > it
> >> > >> yet.
> >> > >> I think the goal was just to take what we have and make it work
> under
> >> > >> Apache infrastructure, then vote on that for 0.1.0.
> >> > >> Although other features like HA or FGS would be great, let's try to
> >> get
> >> > >> our
> >> > >> first Apache release out ASAP.
> >> > >> We can create 0.1.1 or 0.2.0 fix versions for subsequent releases
> >> with
> >> > >> other issues/features. Roadmap would be great.
> >> > >> (I'm just summarizing what we discussed a month or two ago. Feel
> >> free to
> >> > >> correct me or disagree with this approach.)
> >> > >>
> >> > >> On Tue, Aug 4, 2015 at 4:44 PM, Swapnil Daingade <
> >> > >> swapnil.daing...@gmail.com
> >> > >> > wrote:
> >> > >>
> >> > >> > Hi all,
> >> > >> >
> >> > >> > Was wondering what would be the scope for the Myriad 0.1 release.
> >> > >> > It would be nice to have a roadmap page somewhere and target
> >> > >> > features to releases (JIRA 'fix version' field perhaps)
> >> > >> >
> >> > >> > Regards
> >> > >> > Swapnil
> >> > >> >
> >> > >>
> >> > >
> >> > >
> >> >
> >>
> >
> >
>

Reply via email to