Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of discipe@gmail.com designates
 209.85.215.44 as permitted sender)
Mime-Version: 1.0
References: <CC91F7DA.122F2%Dean.Hiller@nrel.gov>
In-Reply-To: <CC91F7DA.122F2%Dean.Hiller@nrel.gov>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:15.0) Gecko/20120907 Thunderbird/15.0.1
Content-Type: multipart/alternative;
	boundary=Apple-Mail-459E8DD5-4601-451C-8093-B571854E84E1
Fcc: imap://discipe%40gmail.com@imap.googlemail.com/[Gmail]/Sent Mail
Message-Id: <AD83906B-26C7-47C9-928E-D48C5589C25E@gmail.com>
Content-Transfer-Encoding: 7bit
From: Vanger <discipe@gmail.com>
Subject: Re: 1000's of CF's.
Date: Mon, 8 Oct 2012 14:02:51 +0400
To: "user@cassandra.apache.org" <user@cassandra.apache.org>


--Apple-Mail-459E8DD5-4601-451C-8093-B571854E84E1
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

So what solution should be for cassandra architecture when we need to make H=
adoop M\R jobs and not be restricted by number of CF?
What we have now is fair amount of CFs  (> 2K) and this number is slowly gro=
wing so we already planing to merge partitioned CFs. But our next goal is to=
 run hadoop tasks on those CFs. All we have is plain Hector and custom ORM o=
n top of it. As far as i understand VirtualKeyspace doesn't help in our case=
.=20
Also i dont understand why not implement support for many CF ( or build-in  p=
artitioning ) on cassandra side. Anybody can explain why this can or cannot b=
e done in cassandra?

Just in case:
We're using cassandra 1.0.11 on 30 nodes (planning upgrade on 1.1.* soon).

--
W/ best regards,=20
Sergey.

On 04.10.2012 0:10, Hiller, Dean wrote:
> Okay, so it only took me two solid days not a week.  PlayOrm in master bra=
nch now supports virtual CF's or virtual tables in ONE CF, so you can have 1=
000's or millions of virtual CF's in one CF now.  It works with all the Scal=
able-SQL, works with the joins, and works with the PlayOrm command line tool=
.
>=20
> Two ways to do it, if you are using the ORM half, you just annotate
>=20
> @NoSqlEntity("MyVirtualCfName")
> @NoSqlVirtualCf(storedInCf=3D"sharedCf")
>=20
> So it's stored in sharedCf with the table name of MyVirtualCfName(in comma=
nd line tool, use MyVirtualCfName to query the table).
>=20
> Then if you don't know your meta data ahead of time, you need to create Db=
oTableMeta and DboColumnMeta objects and save them for every table you creat=
e and can use TypedRow to read and persist (which is what we have a project d=
oing).
>=20
> If you try it out let me know.  We usually get bug fixes in pretty fast if=
 you run into anything.  (more and more questions are forming on stack overf=
low as well ;) ).
>=20
> Later,
> Dean
>=20
>=20


--Apple-Mail-459E8DD5-4601-451C-8093-B571854E84E1
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><span></span></div><div>
  
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  
  
    <div class="moz-cite-prefix">So what solution should be for
      cassandra architecture when we need to make Hadoop M\R jobs and
      not be restricted by number of CF?<br>
      What we have now is fair amount of CFs&nbsp; (&gt; 2K) and this number is slowly growing so we already planing to merge partitioned CFs. But our next goal is to run hadoop tasks on those CFs. All we have is plain Hector and custom ORM on top of it. As far as i understand VirtualKeyspace doesn't help in our case.&nbsp;</div><div class="moz-cite-prefix">Also i dont understand why not implement support for many CF ( or build-in &nbsp;partitioning ) on cassandra side. Anybody can explain why this can or cannot be done in cassandra?</div><div class="moz-cite-prefix"><br></div><div class="moz-cite-prefix">Just in case:</div><div class="moz-cite-prefix">We're using cassandra 1.0.11 on 30 nodes (planning upgrade on 1.1.* soon).<br>
      <br>
      <div class="moz-signature"><span style="color: rgb(164, 72, 164);"><b><i><small>--<br>
                W/ best regards, <br>
                Sergey.</small><br>
              <br>
            </i></b></span></div>
      On 04.10.2012 0:10, Hiller, Dean wrote:<br>
    </div>
    <blockquote cite="mid:CC91F7DA.122F2%25Dean.Hiller@nrel.gov" type="cite">
      <pre wrap="">Okay, so it only took me two solid days not a week.  PlayOrm in master branch now supports virtual CF's or virtual tables in ONE CF, so you can have 1000's or millions of virtual CF's in one CF now.  It works with all the Scalable-SQL, works with the joins, and works with the PlayOrm command line tool.

Two ways to do it, if you are using the ORM half, you just annotate

@NoSqlEntity("MyVirtualCfName")
@NoSqlVirtualCf(storedInCf="sharedCf")

So it's stored in sharedCf with the table name of MyVirtualCfName(in command line tool, use MyVirtualCfName to query the table).

Then if you don't know your meta data ahead of time, you need to create DboTableMeta and DboColumnMeta objects and save them for every table you create and can use TypedRow to read and persist (which is what we have a project doing).

If you try it out let me know.  We usually get bug fixes in pretty fast if you run into anything.  (more and more questions are forming on stack overflow as well ;) ).

Later,
Dean


</pre>
    </blockquote>
    <br>
    <br>
  

</div></body></html>
--Apple-Mail-459E8DD5-4601-451C-8093-B571854E84E1--