Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BEA3810CD9 for ; Wed, 26 Jun 2013 21:22:13 +0000 (UTC) Received: (qmail 89753 invoked by uid 500); 26 Jun 2013 21:22:11 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 89730 invoked by uid 500); 26 Jun 2013 21:22:11 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 89722 invoked by uid 99); 26 Jun 2013 21:22:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jun 2013 21:22:11 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [98.138.90.159] (HELO nm11-vm2.bullet.mail.ne1.yahoo.com) (98.138.90.159) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jun 2013 21:22:05 +0000 Received: from [98.138.101.129] by nm11.bullet.mail.ne1.yahoo.com with NNFMP; 26 Jun 2013 21:21:44 -0000 Received: from [98.138.87.7] by tm17.bullet.mail.ne1.yahoo.com with NNFMP; 26 Jun 2013 21:21:44 -0000 Received: from [127.0.0.1] by omp1007.mail.ne1.yahoo.com with NNFMP; 26 Jun 2013 21:21:44 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 172653.29579.bm@omp1007.mail.ne1.yahoo.com Received: (qmail 15853 invoked by uid 60001); 26 Jun 2013 21:21:44 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1372281704; bh=OfG9JB4cNhqiPE2ZbmBR+3dQZNvIeV2mM56uTLuzc7Y=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=VkzsRUZ/vhzbPlDlnqHqJsKgI6N2LSKQ/386G9YL47HjU4ubn2v/aNKMulc9aOYLmtS40yh8Qs1VQxExE9CZgMma1A5ACH8ClL15Wx0ROhySCO8oSsJEhJG0UXb5W+D4RA/mWKc86AX+/5DtiCFTpN4HWTNt3whOdbfSsHPqACA= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=j/E0HJHF+bpSps6Qy4KD8M2Eez65F8+Aq3qxIZXmlXOH5hB9t9+M18oV5ARiyLUVIknQ6NqOm72WhgPeUy7tZocSlUqtvMZgZqf0eFU5nIHyQ3bcLwHrLHKDDiPIJFQR75k/pGGBzEAu6kDVXU5Uc4VChCOh7d3cBBPYM1qATFk=; X-YMail-OSG: V96dkZAVM1lx9GDIXY4I5B362s2Gar7HK7jT_XDTGrvP1nw KP5Bhg5PpVRfV04NJhWPILkzaUFX_ntpeoINfVZCVamp8VIE7pZpGFrwdFc6 lWYkEF6r3j9_U8I_szoeKn91OqOT78rYm0CtdmBsjvr1H15LMPtClkKXzQpg lpD4BlAcFKPCxkfKtBXGHenZrIz8KKc.441uojdpTi5jLxuZK5JXy2lrQKSk wEuZUblDpqiBr4a8_BxY5SsRoC2R0N.j1w5NQFeDEz33_7t9N4Sj.RRkxm5i EnRRsHyc0tcD4Fl.lkAVwfB3uqciSSBkiproP6UvSX2fO9IL8cM_fMqHrfTG YLxyes6qB5_HmqgUT.bsUMhNyLSkGAJ97zedyACd.wHBivSeeiqg6SsA2hgn bHeP1e4adS5s.OtajaqA1Nii1Ko.B1ql.1r0QuSS93o9PFqSfrbqTmLcjslZ WR0yUYysBKoOscufcuzxEscCRLSi3DHQuRnN.k1xELFT4KOdBjDqEtbPw8Y0 EX6pnk3x3puJF88ZRk9YS3Pcg2lsMj8Uwkkxx4JarLxfPJ.Wm8lQrYw2WTJA KbV02tLd5kyduHpM4PZMixQ5OhWqGNaBMllhxpqB1k29UEhNp.cJCio..Nwk lx78PjKEKWziJsXwOtuiTjcO17Ol_7Ir4UlBA0S.5GVp4M1oAtmHyxtgOGn6 HWgwl5IvfBEv0QCnyEu4vz7RcuEJB5gQ- Received: from [167.234.14.240] by web121805.mail.ne1.yahoo.com via HTTP; Wed, 26 Jun 2013 14:21:43 PDT X-Rocket-MIMEInfo: 002.001,VGhhbmtzIEFydGh1ci4KCkludGVyZXN0aW5nIHlvdSB0aGluayBOb1NRTCBkb2VzIG5vdCBmaXQgaW50byBsYXJnZSB2b2x1bWVzIG9mIGRhdGEsIFRoYXQgaXMgd2hhdCBpdCBpcyB0b3V0ZWQgdG8gZG8uCkkgaGF2ZSBoZWFyZCBQSydzIGFyZSBuZWVkZWQgYnV0IHJlbWVtYmVyIHRoYXQgaXMgd2hhdCB0aGUgImtleSIgY29sdW1uIGlzIGZvciBJIHRob3VnaHQgYW5kIGNvbXBvc2l0ZSBrZXkgc3VwcG9ydCBpcyB0aGVyZSBhbHNvLgoKVGhlIG9ubHkgaXNzdWUgSSBzZWUgaXMgdGhlIGFsbCB0aGF0IGR1cGwBMAEBAQE- X-Mailer: YahooMailWebService/0.8.148.554 References: <1372264767.85242.YahooMailNeo@web121805.mail.ne1.yahoo.com> <1372267240.54860.YahooMailNeo@web121806.mail.ne1.yahoo.com> <1372269336.582.YahooMailNeo@web121805.mail.ne1.yahoo.com> <0A14ED78871B49B3B3805B67FE99142E@vig.local> Message-ID: <1372281703.13985.YahooMailNeo@web121805.mail.ne1.yahoo.com> Date: Wed, 26 Jun 2013 14:21:43 -0700 (PDT) From: Tony Anecito Reply-To: Tony Anecito Subject: Re: Creating an "Index" column... To: Arthur Zubarev , Robert Coli , Users-Cassandra In-Reply-To: <0A14ED78871B49B3B3805B67FE99142E@vig.local> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-465872866-1802120920-1372281703=:13985" X-Virus-Checked: Checked by ClamAV on apache.org ---465872866-1802120920-1372281703=:13985 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Thanks Arthur.=0A=0AInteresting you think NoSQL does not fit into large vol= umes of data, That is what it is touted to do.=0AI have heard PK's are need= ed but remember that is what the "key" column is for I thought and composit= e key support is there also.=0A=0AThe only issue I see is the all that dupl= icate data and a need to keep it in sync. So for example if the movie title= "Superman" changed to "Superman the Man of Steel" you have to go change al= l those duplicate values. An easy problem to solve but the data modeler has= to get past that. lol=0A=0AAcid transactions is the other but I think then= the supplier of info has to think about that one.=0A=0AI have response tim= es in my RDMS of several hundred microseconds which is the really important= requirement for me to keep that the same or better.=0A=0AJust some thought= s on the matter.=0A-Tony=0A=0A=0A=0A________________________________=0A Fro= m: Arthur Zubarev =0ATo: Tony Anecito ; Robert Coli ; Users-Cassandra =0ASent: Wednesday, June 26, 2013 3:08 PM=0ASubject: Re: Cre= ating an "Index" column...=0A =0A=0A=0ATony hi,=0A=A0=0AYes, in some scenar= ios (e.g. a DW), e.g. absence of proper PKs or indexes =0A(just too hard to= envision, you need to think of future queries 1st) getting =0Athru large v= olumes of data makes NoSQL IMHO hard to fit in.=0A=A0=0ABut you have other = choices:=0A=A0=0A1) pagination or=0A2) slice queries.=0A=A0=0ABoth of that = is covered here:=0A=A0=0Ahttp://pkghosh.wordpress.com/2012/03/04/cassandra-= range-query-made-simple/=0A=A0=0AHope that helps.=0A=A0=0A/Arthur=A0=0AFrom= : Tony Anecito =0ASent: Wednesday, June 26, 2013 1:55 PM=0ATo: Robert Coli = ; Users-Cassandra =0ASubject: Re: Creating an "Index" column...=0A=A0 Hi = =0ARobert,=0A=0AActually that is what I did. I did that in my RDMS data mod= el. In =0ACassandra or NOSQL without join or nested selects I have to do tw= o queries. =0AAlso, since batching is not supported on the server side whic= h makes the =0Aperformance worse.=0A=0AI just started learning Cassandra bu= t I am learning =0Afast and there are some challenges when moving to a new = data model driven by =0Athese factors.=0A=0ARegards,=0A-Tony=0A=0A=0A=A0=0A= =0A________________________________=0A From: Robert Coli =0ATo: user@cassandra.apache.org; Tony Anecito =0A= =0ASent: Wednesday, June 26, 2013 11:32 =0AAM=0ASubject: Re: Creating an = =0A"Index" column...=0A=0A=0AOn Wed, Jun 26, 2013 at 10:20 AM, Tony Anecito= =0A wrote:=0A> =0ANever mind I figured it out. I foun= d it via a search for Secondary =0Aindexes.=0A=0AIn general unless you actu= ally need atomic update of the row and =0Aits=0Asecondary index, you are pr= obably better off creating your own =0Apseudo=0Asecondary index column =0Af= amily.=0A=0A=3DRob ---465872866-1802120920-1372281703=:13985 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Thanks Art= hur.

Interesting you thi= nk NoSQL does not fit into large volumes of data, That is what it is touted= to do.
I have heard PK's are needed but remember th= at is what the "key" column is for I thought and composite key support is t= here also.

The only iss= ue I see is the all that duplicate data and a need to keep it in sync. So f= or example if the movie title "Superman" changed to "Superman the Man of St= eel" you have to go change all those duplicate values. An easy problem to s= olve but the data modeler has to get past that. lol

<= span>
Acid transactions is the other but I think then the supplier of info has to think about that one.
I have response times in my RDMS of several= hundred microseconds which is the really important requirement for me to k= eep that the same or better.

<= span>Just some thoughts on the matter.
-Tony
=

From: Arthur Zubarev <Arthur.Zubarev@Aol.com>
<= span style=3D"font-weight: bold;">To: Tony Anecito <adanecito= @yahoo.com>; Robert Coli <rcoli@eventbrite.com>; Users-Cassandra &= lt;user@cassandra.apache.org>
Sent: Wednesday, June 26, 2013 3:08 PM
Subject: Re: Creating an "Index" column...
=

=0A
=0A
=0A
=0A
Tony hi,
=0A
 =0A
Yes, in some scenarios (e.g. a DW), e.g. absence of proper PKs = or indexes =0A(just too hard to envision, you need to think of future queri= es 1st) getting =0Athru large volumes of data makes NoSQL IMHO hard to fit = in.
=0A
 
=0A
But you have other choices:
=0A 
=0A
1) pagination or
=0A
2) slice queries.=0A
 
=0A
Both of that is covered here:
=0A
&nb= sp;
=0A=0A
 
=0A
Hope that = helps.
=0A
 
=0A
/Arthur
=0A
=0A
=0A
 
=0A
=0A=0A
Sent: Wednesday, June= 26, 2013 1:55 PM
=0A=0A
Subject: Re: Creating an "Index" column...=
=0A
 
=0A
=0A
Hi =0ARobert,

Actually that is what I did. I did that in my R= DMS data model. In =0ACassandra or NOSQL without join or nested selects I h= ave to do two queries. =0AAlso, since batching is not supported on the serv= er side which makes the =0Aperformance worse.

I just started learnin= g Cassandra but I am learning =0Afast and there are some challenges when mo= ving to a new data model driven by =0Athese factors.

Regards,
-To= ny
=0A

=0A
 
=0A
=0A=0A
=0A
=0AFrom: =0ARobert Coli <= rcoli@eventbrite.com>
To:= user@cassandra.apache.org; Tony Anecito =0A<adanecito@yahoo.com>=
Sent: Wednesday, June = 26, 2013 11:32 =0AAM
Subject: Re: Creating an =0A"Index" column...
=0A

On Wed, Jun 26, 2013 at 10:20 AM, Tony A= necito =0A<adanecito@yahoo.com= > wrote:
> =0ANever mind I figured it out. I found it via a search= for Secondary =0Aindexes.

In general unless you actually need atomi= c update of the row and =0Aits
secondary index, you are probably better = off creating your own =0Apseudo
secondary index column =0Afamily.
=3DRob



---465872866-1802120920-1372281703=:13985--