On Mon, Jul 25, 2011 at 6:10 PM, Doug Meil <[email protected]>wrote:

>
> Andrew:  nicely put.
>
> Jeff W:  I agree with your ordering.
>
> Stack:  I agree with the book change for inclusion, and I agree with the
> caveat about 'free as in free beer'.
>

+1, seems entirely reasonable to list compatible alternatives in our docs.


>
> Todd/Ryan:  regarding the book reference to CDH, I think the CDH reference
> being 'free as in beer' reference is an important differentiator, if it
> wasn't it would be a different story.
>

To nit-pick, CDH is free-as-in-speech as well as free-as-in-beer, since it's
under an Apache 2.0 license, same as HBase.


>
>
> Ted:  re: "My only test for these would be something that helps hbase
> users", I agree with the intent,  as long as the available license isn't
> only commercial.
>
>
>
>
> On 7/25/11 8:43 PM, "Andrew Purtell" <[email protected]> wrote:
>
> >I agree it's a fine line. As far as vendor specific pronouncements, may I
> >suggest a little goes a long way, quality over quantity.
> >
> >In my opinion it's never sufficient to say only "nonopen product Foo does
> >X" on an open source project's user list. Instead you need to first
> >explain how to do X with available FOSS tools. After that, mentioning
> >that Foo does it out of the box and is therefore easier than the
> >explained FOSS option is totally acceptable.
> >
> >Best regards,
> >
> >
> >   - Andy
> >
> >Problems worthy of attack prove their worth by hitting back. - Piet Hein
> >(via Tom White)
> >
> >
> >----- Original Message -----
> >> From: Todd Lipcon <[email protected]>
> >> To: [email protected]
> >> Cc:
> >> Sent: Monday, July 25, 2011 11:45 AM
> >> Subject: Re: Monitoring
> >>
> >> On Mon, Jul 25, 2011 at 11:28 AM, Ted Dunning <[email protected]>
> >> wrote:
> >>
> >>>  I am very sympathetic here.  Also, somewhat linguistically challenged
> >>>on
> >>>  this point since there is a fine line to be walked.  All suggestions
> >>>are
> >>>  welcome.
> >>>
> >>>  How should I answer this?  The question was "how can I get alerts for
> >> my
> >>>  hbase cluster"?
> >>>
> >>>  One answer is definitely MapR.  Is there a way to say that without
> >>>being a
> >>>  excessively pluggy?
> >>>
> >>>  Another answer that I want to underscore is "MapR supports Hbase.  A
> >> lot."
> >>>
> >>
> >> The issue is that I might be then tempted to start arguing that Cloudera
> >> Enterprise supports HBase better than MapR. Then we devolve into an
> >>annoying
> >> vendor war which doesn't help anyone.
> >>
> >> Best to just set a policy and stick to it for public responses. I don't
> >>see
> >> anything wrong with your replying off-list to the requester with a sales
> >> pitch. This provides the information that might help the user without
> >> risking polluting the -user list with a lot of discussion of commercial
> >> products.
> >>
> >> -Todd
> >>
> >>
> >>>
> >>>  On Mon, Jul 25, 2011 at 11:09 AM, Stack <[email protected]> wrote:
> >>>
> >>>  > On Mon, Jul 25, 2011 at 8:54 AM, Ted Dunning
> >> <[email protected]>
> >>>  > wrote:
> >>>  > > Slightly off topic, but MapR runs Hbase very handily (several
> >> times
> >>>  > faster,
> >>>  > > in fact) and provides comprehensive monitoring and alerting out
> >> of the
> >>>  > box.
> >>>  > >
> >>>  >
> >>>  > Hey Ted:
> >>>  >
> >>>  > MapR is good stuff indeed but the above can be read as a raw plug
> >>>for
> >>>  > a non-open-source/commercial product.
> >>>  >
> >>>  > I'd like to petition that you go easy with messages that could
> >>>  > possibly be interpreted so.  Other, not-such-close-in-friends of
> >>>  > hbase, seeing 'commerical' messages up on our list might take it as
> >>>  > license to dump  their commercial messages for tech related, or not,
> >>>  > into hbase mailing lists.  A list riddled with commerical messages
> >>>  > would likely sour many who are subscribed here.
> >>>  >
> >>>  > Thanks boss,
> >>>  > St.Ack
> >>>  >
> >>>
> >>
> >>
> >>
> >> --
> >> Todd Lipcon
> >> Software Engineer, Cloudera
> >>
>
>


-- 
Todd Lipcon
Software Engineer, Cloudera

Reply via email to