[
https://issues.apache.org/jira/browse/SPARK-14942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apache Spark reassigned SPARK-14942:
------------------------------------
Assignee: (was: Apache Spark)
> First construct a batch then run the batch for continuous queries
> -----------------------------------------------------------------
>
> Key: SPARK-14942
> URL: https://issues.apache.org/jira/browse/SPARK-14942
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.0.0
> Reporter: Liwei Lin
>
> Currently in {{StreamExecution}}, we first run the batch, then construct the
> next:
> {code}
> if (dataAvailable) runBatch()
> constructNextBatch()
> {code}
> This is good if we run batches ASAP, where data would get processed in the
> very next batch:
> !https://cloud.githubusercontent.com/assets/15843379/14779964/2786e698-0b0d-11e6-9d2c-bb41513488b2.png!
> However, if we run batches at trigger like {{ProcessTime("1 minute")}}, data
> - such as y below - may not get processed in the very next batch i.e. batch
> 1, but in batch 2:
> !https://cloud.githubusercontent.com/assets/15843379/14779818/6f3bb064-0b0c-11e6-9f16-c1ce4897186b.png!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
