You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Dave Brosius (JIRA)" <ji...@apache.org> on 2013/06/21 03:25:24 UTC
[jira] [Resolved] (CASSANDRA-5286) Streaming 2.0
[ https://issues.apache.org/jira/browse/CASSANDRA-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Brosius resolved CASSANDRA-5286.
-------------------------------------
Resolution: Fixed
addendum applied to trunk as 56d2296adf281b774aea6598bd8baaa9e77685f3
> Streaming 2.0
> -------------
>
> Key: CASSANDRA-5286
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5286
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Yuki Morishita
> Assignee: Yuki Morishita
> Labels: streaming
> Fix For: 2.0 beta 1
>
> Attachments: 5286_addendum.txt
>
>
> 2.0 is the good time to redesign streaming API including protocol to make streaming more performant and reliable.
> Design goals that come up in my mind:
> *Better performance*
> - Protocol optimization
> - Stream multiple files in parallel (CASSANDRA-4663)
> - Persistent connection (CASSANDRA-4660)
> *Better control*
> - Cleaner API for error handling
> - Integrate both IN/OUT streams into one session, so the components(bootstrap, move, bulkload, repair...) that use streaming can manage them easily.
> *Better reporting*
> - Better logging/tracing
> - More metrics
> - Progress reporting API for external client
--
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