[
https://issues.apache.org/jira/browse/CASSANDRA-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130768#comment-13130768
]
Jonathan Ellis commented on CASSANDRA-3383:
-------------------------------------------
My reaction would be that
1) if you really have different data sets involved, the "right" solution would
be to split those into different CFs
2) but if you have the same data set where some outlier rows are much larger
than others then a "query cache" like CASSANDRA-1956 might be a good general
purpose solution
> Make Row cache reject wide rows which are more than x columns
> -------------------------------------------------------------
>
> Key: CASSANDRA-3383
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3383
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.1
> Environment: Linux with Sun JDK
> Reporter: Vijay
> Assignee: Vijay
> Priority: Minor
>
> The problem with the row cache is it has to cache the whole row into the
> memory, this works great for small rows but not for the wide rows. Even
> off-heap cache has to read everything into the heap eventually causing GC
> overhead (If your query is to get few columns).
> It will be nice to reject the rows which are bigger than x columns (This can
> be a KS setting).... this will help cases where we have mixed load of small
> and wide column datasets in the same cf.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
