You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sachin Aggarwal (JIRA)" <ji...@apache.org> on 2016/05/06 15:46:12 UTC

[jira] [Commented] (SPARK-15183) adding outputMode to structure Streaming Experimental Api

    [ https://issues.apache.org/jira/browse/SPARK-15183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274241#comment-15274241 ] 

Sachin Aggarwal commented on SPARK-15183:
-----------------------------------------

please mark closed if not qualifies for jira

> adding outputMode to structure Streaming Experimental Api
> ---------------------------------------------------------
>
>                 Key: SPARK-15183
>                 URL: https://issues.apache.org/jira/browse/SPARK-15183
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL, Streaming
>            Reporter: Sachin Aggarwal
>            Priority: Trivial
>
> while experimenting with structure streaming. I found that mode() is used for non-continuous queries while outputMode() is used for continuous queries.
> ouputMode is not defined, so I have written the some raw implementation and test cases just to make sure the streaming app works 
> Note:-
> /** Start a query */
>   private[sql] def startQuery(
>       name: String,
>       checkpointLocation: String,
>       df: DataFrame,
>       sink: Sink,
>       trigger: Trigger = ProcessingTime(0),
>       triggerClock: Clock = new SystemClock(),
>       outputMode: OutputMode = Append): ContinuousQuery = {
> As per me outputMode should be defined before triggerClock, the constructor with  outputMode defined will be used more often then triggerClock.
> I have added triggerClock() method also 



--
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