I mean "balance the risk aversion against the value of new features" duh.
On Wed, Mar 5, 2014 at 1:39 PM, Andrew Musselman <andrew.mussel...@gmail.com > wrote: > Yeah, for sure; balancing clients' risk aversion to technical features is > why we often recommend vendor solutions. > > Having a little button to choose a newer version of a component in the > Manager UI (even with a confirmation dialog that said "Are you sure? Are > you crazy?") would be more palatable to some teams than installing > tarballs, is what I'm getting at. > > > On Wed, Mar 5, 2014 at 1:30 PM, Sean Owen <sro...@gmail.com> wrote: > >> You can always install whatever version of anything on your cluster >> that you want. It may or may not work, but often happens to, at least >> for whatever you need it to do. >> >> It's just the same as it is without a packaged distribution -- dump >> new tarballs and cross your fingers. Nothing is weird or different >> about the setup or layout. That is the "here be dragons" solution, >> already >> >> You go with support from a packaged distribution when you want a "here >> be no dragons" solution. Everything else is by definition already >> something you can and should do yourself outside of a packaged >> distribution. And really -- you freely can, and it's not hard, if you >> know what you are doing. >> >> On Wed, Mar 5, 2014 at 9:15 PM, Andrew Musselman >> <andrew.mussel...@gmail.com> wrote: >> > Feels like just yesterday :) >> > >> > Consider this a feature request to have more flexible component >> versioning, >> > even with a caveat/"here be dragons" warning. I know that complicates >> > things but people do use your releases a long time. I personally >> wished I >> > could upgrade Pig on CDH 4 for new features but there was no simple way >> on >> > a managed cluster. >> > >> > >> > On Wed, Mar 5, 2014 at 12:12 PM, Sean Owen <sro...@gmail.com> wrote: >> > >> >> I don't understand this -- CDH always bundles the latest release. >> >> >> >> You know that CDH4 was released in July 2012, right? So it included >> >> 0.7 + patches. CDH5 includes 0.8 because 0.9 was released about a >> >> month after it began beta 2. >> >> >> >> CDH follows semantic versioning and won't introduce changes that are >> >> not backwards-compatible in a minor version update. 0.x releases of >> >> Mahout act like major version changes -- not backwards compatible. So >> >> 4.x will always be 0.7 and 5.x will always be 0.8. >> >> >> >> On Wed, Mar 5, 2014 at 5:34 PM, Dmitriy Lyubimov <dlie...@gmail.com> >> >> wrote: >> >> > On Wed, Mar 5, 2014 at 9:08 AM, Sean Owen <sro...@gmail.com> wrote: >> >> > >> >> >> I don't follow what here makes you say they are "cut down" releases? >> >> >> >> >> > >> >> > meaning it seems to be pretty much 2 releases behind the official. >> But i >> >> > definitely don't follow CDH developments in this department, you >> seem in >> >> a >> >> > better position to explain the existing patchlevel there so I defer >> to >> >> you >> >> > to explain why this patchlevel is not there. >> >> > >> >> > -d >> >> >> > >
