just opened https://issues.apache.org/jira/browse/ZEPPELIN-274 to track this proposal.
@Henry, IMO the issue is not related to the underlying streaming platforms which provides various means for tracking the status as it is with the Zeppelin lifecycle model which doesn't provide abstractions to support long-running jobs. See the JIRA ticket for additional info. On 30 August 2015 at 03:17, Henry Saputra <[email protected]> wrote: > So what is need from any underlying streaming framework to support > this on Zeppelin? > I guess something like state updates for each record processed? > > On Fri, Aug 28, 2015 at 7:53 AM, Christian Tzolov <[email protected]> > wrote: > > I've been exploring lately how would a streaming platforms fit into > > Zeppelin. > > > > The streaming processes are continuous as opposed to the usual > Paragraph's > > batch like jobs. > > > > For example you start the twitter search stream in a paragraph (by > clicking > > the Run button) the underlying streaming platform will open a stream and > > will return and the Paragraph will show a 'FINISHED' state while the real > > state in this case is 'STARTED' (or alike)? > > > > Currently Zeppelin doesn't seem to provide abstractions to track and stop > > such long-living tasks? > > > > I've checked the Spark Streaming tutorial but couldn't find an > explanation > > of how to track and stop running streams? > > > > Do you think this is a valid use case for Zeppelin? Perhaps Spark > Streaming > > and Flink have already solved this somehow? > > > > If you think this is valid use case i will open a JIRA ticket so we can > > start looking for solutions. > > > > Cheers, > > Christian > > > > -- > > Christian Tzolov <http://www.linkedin.com/in/tzolov> | Solution > Architect, > > EMEA Practice Team | Pivotal <http://pivotal.io/> > > [email protected]|+31610285517 > -- Christian Tzolov <http://www.linkedin.com/in/tzolov> | Solution Architect, EMEA Practice Team | Pivotal <http://pivotal.io/> [email protected]|+31610285517
