To clarify, I haven't tested it with compact storage, but it will only use the first part of the primary key without compact storage.
Actually, my solution only makes a row for each unique value of the first part of the primary key.On Jul 6, 2012 3:07 PM, "Leonid Ilyevsky" <firstname.lastname@example.org> wrote:
Thanks Derek, I actually saw your post, but this is not a good substitution for a real dynamic table. Your trick will make a table with even more rows; I wanted wide rows so the reads and writes would be more efficient.
On Fri, Jul 6, 2012 at 2:49 PM, Leonid Ilyevsky <email@example.com> wrote:
At this point I am really confused about what direction Cassandra is going. CQL 3 has the benefit of composite keys, but no dynamic columns.
I thought, the whole point of Cassandra was to provide dynamic tables.
See my earlier post on the subject:
You can have a dynamic table with CQL3, you just can't have a table with a mix of dynamic/nondynamic columns.
This email, along with any attachments, is confidential and may be legally privileged or otherwise protected from disclosure. Any unauthorized dissemination, copying or use of the contents of this email is strictly prohibited and may be in violation of law. If you are not the intended recipient, any disclosure, copying, forwarding or distribution of this email is strictly prohibited and this email and any attachments should be deleted immediately. This email and any attachments do not constitute an offer to sell or a solicitation of an offer to purchase any interest in any investment vehicle sponsored by Moon Capital Management LP (“Moon Capital”). Moon Capital does not provide legal, accounting or tax advice. Any statement regarding legal, accounting or tax matters was not intended or written to be relied upon by any person as advice. Moon Capital does not waive confidentiality or privilege as a result of this email.