cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-579) Add support to io.Streaming API for sending Streams
Date Fri, 29 Jan 2010 23:25:34 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806558#action_12806558
] 

Jonathan Ellis commented on CASSANDRA-579:
------------------------------------------

Note that if we're streaming w/o first writing temporary file locally there is less reason
to keep all outbound streaming single-threaded, but Streaming contexts currently assume there
can only be one outstanding stream per source node.  So keep that in mind if we are tempted
to multithread streaming.

> Add support to io.Streaming API for sending Streams
> ---------------------------------------------------
>
>                 Key: CASSANDRA-579
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-579
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Stu Hood
>             Fix For: 0.7
>
>
> The io.Streaming API currently requires a file on disk to stream, which means that bootstrap
and repairs need to perform an anti-compaction that writes a bunch of data to disk, only to
have it be deleted after the streaming has finished.
> Ideally, the Streaming API should allow for streaming from an InputStream (or any other
class we think we need to design to make the streaming as efficient as possible). That way,
anti-compaction for repair/bootstrap does not perform any writing: it simply streams the relevant
portion of the file to the neighbor.
> Additionally, this opens up interesting possibilities, such as providing the Streaming
API as a (Java only?) client API. One use case would be for a Hadoop OutputFormat: rather
than writing BinaryMemtables, the OutputFormat could literally write an SSTable to the stream.
This might require better integration with gossip, to ensure that you aren't writing to the
completely wrong node.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message