Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
In-Reply-To: 
 <CAENxBwxiQRzWnRKbh_3D38Hkx-9gjnCTXAJAxKL=mP76+7Zkhw@mail.gmail.com>
References: 
 <CAGA++nkTyQXKCsBe=Dzjc8Cy4TpWwJc0ARY-0nLC0iqXdR0jfQ@mail.gmail.com>
	<CAKkz8Q2UwYy6AbRjFwoavFLcr5jEHELR-QYcmuXVJ7rG6nxwwQ@mail.gmail.com>
	<CAGA++nmaJJ4QT8ygMxQgALmqiEb_meW_wHKEcELM602Kyjvt6A@mail.gmail.com>
	<CAKkz8Q1UM92Ga0+eNaxV5KzXcS+hcSA87cCGc12LMP=CWCppog@mail.gmail.com>
	<CAENxBwwm9CRiOp_zs-2ru3bezTg5FznMxZGMt8GjBs-SDjghww@mail.gmail.com>
	<CAKkz8Q3Q8hfG1jQ23kj4GJM+i7xMiG56Oczm7PQ=w1rsjiOOtw@mail.gmail.com>
	<CAEDUwd203hWizR_QTt19su2F90de9ccCFnXXFQrD3BO9g4ZPiA@mail.gmail.com>
	<CAENxBwxiQRzWnRKbh_3D38Hkx-9gjnCTXAJAxKL=mP76+7Zkhw@mail.gmail.com>
Date: Thu, 20 Feb 2014 20:27:20 -0500
Message-ID: 
 <CAKgmDnEZ=f7AuhJN_TNKYCpegnBahNP83W_NFXhLoJm9OP5AtQ@mail.gmail.com>
Subject: Re: Performance problem with large wide row inserts using CQL
From: "Laing, Michael" <michael.laing@nytimes.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a113a945aecb9c904f2e085e1

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

Just to add my 2 cents...

We are very happy CQL users, running in production.

I have had no problems modeling whatever I have needed to, including
problems similar to the examples set forth previously, in CQL.

Personally I think it is an excellent improvement to Cassandra, and we have
no intentions to ever look back to thrift.

Michael Laing
Systems Architect
NYTimes


On Thu, Feb 20, 2014 at 7:49 PM, Edward Capriolo <edlinuxguru@gmail.com>wro=
te:

>
>
> On Thursday, February 20, 2014, Robert Coli <rcoli@eventbrite.com> wrote:
> > On Thu, Feb 20, 2014 at 9:12 AM, Sylvain Lebresne <sylvain@datastax.com=
>
> wrote:
> >>
> >> Of course, if everyone was using that reasoning, no-one would ever tes=
t
> new features and report problems/suggest improvement. So thanks to anyone
> like R=C3=BCdiger that actually tries stuff and take the time to report p=
roblems
> when they think they encounter one. Keep at it, *you* are the one helping
> Cassandra to get better everyday.
> >
> >
> > Perhaps people who are prototyping their first application with a piece
> of software are not the ideal people to beta test it?
> >
> > The people catching new version bullets for the community should be
> experienced operators choosing to do so in development and staging
> environments.
> > The current paradigm ensures that new users have to deal with Cassandra
> problems that interfere with their prototyping process and initial
> production deploy, presumably getting a very bad initial impression of
> Cassandra in the process.
> > =3DRob
> >
>
> You would be surprised how many people pick software a of software b base=
d
> on initial impressions.
>
> The reason I ended up choosing cassandra over hbase mostly boilded down t=
o
> c* being easy to set up and not crashing. If it took us say 3 days to sta=
nd
> up a cassandra cluster and do the hello world thing i might very well be =
a
> voldemort user!
>
>
>
>
>
>
> --
> Sorry this was sent from mobile. Will do less grammar and spell check tha=
n
> usual.
>

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

<div dir=3D"ltr">Just to add my 2 cents...<div><br></div><div>We are very h=
appy CQL users, running in production.</div><div><br></div><div>I have had =
no problems modeling whatever I have needed to, including problems similar =
to the examples set forth previously, in CQL.</div>
<div><br></div><div>Personally I think it is an excellent improvement to Ca=
ssandra, and we have no intentions to ever look back to thrift.</div><div><=
br></div><div>Michael Laing</div><div>Systems Architect</div><div>NYTimes</=
div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu,=
 Feb 20, 2014 at 7:49 PM, Edward Capriolo <span dir=3D"ltr">&lt;<a href=3D"=
mailto:edlinuxguru@gmail.com" target=3D"_blank">edlinuxguru@gmail.com</a>&g=
t;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5"><br>=
<br>On Thursday, February 20, 2014, Robert Coli &lt;<a href=3D"mailto:rcoli=
@eventbrite.com" target=3D"_blank">rcoli@eventbrite.com</a>&gt; wrote:<br>
&gt; On Thu, Feb 20, 2014 at 9:12 AM, Sylvain Lebresne &lt;<a href=3D"mailt=
o:sylvain@datastax.com" target=3D"_blank">sylvain@datastax.com</a>&gt; wrot=
e:<br>
&gt;&gt;<br>&gt;&gt; Of course, if everyone was using that reasoning, no-on=
e would ever test new features and report problems/suggest improvement. So =
thanks to anyone like R=C3=BCdiger that actually tries stuff and take the t=
ime to report problems when they think they encounter one. Keep at it, *you=
* are the one helping Cassandra to get better everyday. =C2=A0<br>

&gt;<br>&gt; =C2=A0=C2=A0<br>&gt; Perhaps people who are prototyping their =
first application with a piece of software are not the ideal people to beta=
 test it?<br>&gt;<br>&gt; The people catching new version bullets for the c=
ommunity should be experienced operators choosing to do so in development a=
nd staging environments.<br>

&gt; The current paradigm ensures that new users have to deal with Cassandr=
a problems that interfere with their prototyping process and initial produc=
tion deploy, presumably getting a very bad initial impression of Cassandra =
in the process.<br>

&gt; =3DRob<br>&gt;<br><br></div></div>You would be surprised how many peop=
le pick software a of software b based on initial impressions.<br><br>The r=
eason I ended up choosing cassandra over hbase mostly boilded down to c* be=
ing easy to set up and not crashing. If it took us say 3 days to stand up a=
 cassandra cluster and do the hello world thing i might very well be a vold=
emort user!<div class=3D"HOEnZb">
<div class=3D"h5"><br>
<br><br><br><br><br>-- <br>Sorry this was sent from mobile. Will do less gr=
ammar and spell check than usual.<br>
</div></div></blockquote></div><br></div>

--001a113a945aecb9c904f2e085e1--