[
https://issues.apache.org/jira/browse/CASSANDRA-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119674#comment-13119674
]
Jonathan Ellis commented on CASSANDRA-3264:
-------------------------------------------
bq. I think this is a big enough issue for folks running with timeseries type
data that we should fix it before we jump to CQL
Really? m/r support is almost two years old, let's not exaggerate how much of
a problem this is.
bq. I'm not suggested we jump to CQL, just implement the same idea.
I don't think hacking CFIF apart to support paging with some one-off transpose
hack, then again to support "real" CQL transpose, is a good use of time.
> Add wide row paging for ColumnFamilyInputFormat and ColumnFamilyOutputFormat
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-3264
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3264
> Project: Cassandra
> Issue Type: Improvement
> Components: Hadoop
> Reporter: T Jake Luciani
> Labels: lhf
> Fix For: 0.8.7
>
>
> Hadoop input/output formats currently can OOM on wide rows.
> We can add a new option to the ConfigHelper like columnPagingSize with a
> default of Integer.MAX_VALUE.
> The input format would page the row internally rather than pull it over at
> once.
> The output format could also use this to avoid sending huge rows over at once.
--
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
