You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Shixiong Zhu (JIRA)" <ji...@apache.org> on 2016/10/27 17:31:58 UTC

[jira] [Resolved] (SPARK-17813) Maximum data per trigger

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

Shixiong Zhu resolved SPARK-17813.
----------------------------------
       Resolution: Fixed
         Assignee: Cody Koeninger
    Fix Version/s: 2.1.0
                   2.0.3

> Maximum data per trigger
> ------------------------
>
>                 Key: SPARK-17813
>                 URL: https://issues.apache.org/jira/browse/SPARK-17813
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>            Reporter: Michael Armbrust
>            Assignee: Cody Koeninger
>             Fix For: 2.0.3, 2.1.0
>
>
> At any given point in a streaming query execution, we process all available data.  This maximizes throughput at the cost of latency.  We should add something similar to the {{maxFilesPerTrigger}} option available for files.



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