d be deleted. This could be done in some sort of
>> background data maintenance job that runs periodically. Even if it is a
>> low-priority background job it look like it will create a lot overhead
>> (scanning and producing counts).
>>
>>
>>
>> John
>
>
>
>
> John
>
> *From:* Edward Capriolo [mailto:edlinuxg...@gmail.com]
> *Sent:* Wednesday, February 26, 2014 5:56 AM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Naive question about orphan rows
>
>
>
> It is probably ok to have redundant songs in playlists,
edlinuxg...@gmail.com]
Sent: Wednesday, February 26, 2014 5:56 AM
To: user@cassandra.apache.org
Subject: Re: Naive question about orphan rows
It is probably ok to have redundant songs in playlists, cassandra is about
denormalization.
Dealing with this issue is going to be hard since the only w
It is probably ok to have redundant songs in playlists, cassandra is about
denormalization.
Dealing with this issue is going to be hard since the only way to dwal with
this would be scanning through the firsr cf and procing counts then using
that information to delete in the second table. However
