Thanks.
But I think sometimes we need to do it, because by this way, we don't have
to change the current CFs(assume we already have two CFs, and don't want to
build a new one).
Alvin
2010/9/11 aaron morton
> I cannot tell you where in the code to make these changes. But it sounds
> like you wan
I cannot tell you where in the code to make these changes. But it sounds like
you want to fork cassandra and turn it into a RDBMS. It would undoubtedly be
easier to just use a RDBMS.
Rather than have two CF's, address and name, just have one for the person using
a super CF. Pull back the entire
Hello,
I am going to build an index to join two CFs.
First, we see this index as a CF/SCF. The difference is I don't materialise
it.
Assume we have two tables:
ID_Address(*Id*, address) , Name_ID(*name*, id)
Then,the index is: Name_Address(*name*, address)
When the application tries to query on
Sounds fine to me.
On Fri, Sep 10, 2010 at 10:34 AM, Amol Deshpande
wrote:
> Hi,
> I noticed a lot of common code in the thrift and avro
> CassandraDaemon.setup methods. Would it be possible to move those into a
> commonSetup() method in the AbstractCassandraDaemon class ? This will be
> helpful
Hi,
I noticed a lot of common code in the thrift and avro
CassandraDaemon.setup methods. Would it be possible to move those into a
commonSetup() method in the AbstractCassandraDaemon class ? This will be
helpful when I add a protocol buffer client-facing interface.
I just tried that and in a quick
