You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Ashish Paliwal (JIRA)" <ji...@apache.org> on 2013/12/12 13:49:09 UTC
[jira] [Commented] (FLUME-1286) Storm Sink
[ https://issues.apache.org/jira/browse/FLUME-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846286#comment-13846286 ]
Ashish Paliwal commented on FLUME-1286:
---------------------------------------
Started working on this. Technically we cannot call it "Storm Sink", as Sink's lifecycle is managed by Flume, whereas Storm Spout has it's own lifecycle managed by Storm.
It would need to be build as some kind of connector between Flume Sink and Storm spout. If we have Kafka Sink, Kafka spout can be used. Or we use an embedded agent inside Spout, and drain the Channel inside nextTuple() method.
Shall play around a bit more with Storm and try to explore other approaches as well. If anyone has got some ideas, would be great to discuss.
> Storm Sink
> ----------
>
> Key: FLUME-1286
> URL: https://issues.apache.org/jira/browse/FLUME-1286
> Project: Flume
> Issue Type: New Feature
> Components: Sinks+Sources
> Reporter: Mubarak Seyed
> Assignee: Ashish Paliwal
>
> Storm contrib project explains how to push/emit events to storm spout [1]. It would be nice to create a flume-storm sink to emit events to storm spout output collector [2]
> [1] https://github.com/nathanmarz/storm-contrib/tree/master/storm-scribe
> [2] https://github.com/nathanmarz/storm-contrib/blob/master/storm-scribe/src/jvm/storm/scribe/ScribeSpout.java
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)