spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SPARK-15227) InputStream stop-start semantics + empty implementations
Date Tue, 17 May 2016 09:06:12 GMT

     [ https://issues.apache.org/jira/browse/SPARK-15227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sean Owen resolved SPARK-15227.
-------------------------------
    Resolution: Not A Problem

A fine question, but really should go to user@

> InputStream stop-start semantics + empty implementations
> --------------------------------------------------------
>
>                 Key: SPARK-15227
>                 URL: https://issues.apache.org/jira/browse/SPARK-15227
>             Project: Spark
>          Issue Type: Improvement
>          Components: Input/Output, Streaming
>    Affects Versions: 1.6.1
>            Reporter: Stas Levin
>            Priority: Minor
>
> Hi,
> Seems like quite a few InputStream(s) currently leave the start and stop methods empty.

> I was hoping to hear your thoughts on:
> 1. Whether there were any particular reasons to leave these methods empty ?
> 2. Do the stop/start semantics of InputStream(s) aim to support pause-resume use-cases,
or is it a one way ticket? 
> A pause-resume kind of thing could be really useful for cases where one wishes to load
new offline data for the streaming app to run on top of, without restarting the entire app.
> Thanks a lot,
> Stas



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message