[
https://issues.apache.org/jira/browse/CASSANDRA-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593738#comment-13593738
]
Ahmet AKYOL commented on CASSANDRA-3929:
----------------------------------------
[~rbranson]: thanks for the explanation. I also want to "get it for free" but
what I tried to say is "as a user, I am OK with extra cql if it's necessary " .
I was thinking something similar to a redis pipeline which starts with adding
data with zadd and after that limiting data with zremrangeByRank as in your
words "if the data is time-ordered ...".
About the requirement "reading the entire row", let's first revisit our use
cases for this "limited row size type tables". Why we want them? Most probably
we already have tables for our "big data" (that's why we use and love C*), but
we need a special cache for "hot data" that's why it's a blocker to move from
Redis to C* for some storage. So, what about C*'s row cache ? unfortunately,
not an option because we may need data from many tables or we need only (most
recent) portion of the wide rows, not all of them. So,once again, what we
really want from this issue is indeed, a "special cache table" and that's why
"reading the entire row" is not a problem beacuse we want the entire row on
memory when it's hot.
once more, just my two cents, no intention to interrupt your development
process. Just see me as the business (user) side and remember the principle
"business people and developers must work together daily throughout the
project" of [agile manifesto|http://agilemanifesto.org/principles.html]
> Support row size limits
> -----------------------
>
> Key: CASSANDRA-3929
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3929
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Dave Brosius
> Priority: Minor
> Labels: ponies
> Fix For: 2.0
>
> Attachments: 3929_b.txt, 3929_c.txt, 3929_d.txt, 3929_e.txt,
> 3929_f.txt, 3929_g_tests.txt, 3929_g.txt, 3929.txt
>
>
> We currently support expiring columns by time-to-live; we've also had
> requests for keeping the most recent N columns in a row.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
