You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Tathagata Das (JIRA)" <ji...@apache.org> on 2017/07/12 07:40:00 UTC
[jira] [Resolved] (SPARK-21370) Avoid doing anything on
HDFSBackedStateStore.abort() when there are no updates to commit
[ https://issues.apache.org/jira/browse/SPARK-21370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tathagata Das resolved SPARK-21370.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.3.0
Issue resolved by pull request 18603
[https://github.com/apache/spark/pull/18603]
> Avoid doing anything on HDFSBackedStateStore.abort() when there are no updates to commit
> ----------------------------------------------------------------------------------------
>
> Key: SPARK-21370
> URL: https://issues.apache.org/jira/browse/SPARK-21370
> Project: Spark
> Issue Type: Test
> Components: Structured Streaming
> Affects Versions: 2.1.1
> Reporter: Burak Yavuz
> Assignee: Burak Yavuz
> Priority: Minor
> Fix For: 2.3.0
>
>
> During Streaming Aggregation, we have two StateStores per task, one used as read-only in StateStoreRestoreExec, and one read-write used in `StateStoreSaveExec`. `StateStore.abort` will be called for these StateStores if they haven't committed their results. We need to make sure that abort in read-only store after a commit in the read-write store doesn't
> accidentally lead to the deletion of state.
> This JIRA proposes a test for this case. StateStore implementations should successfully handle this use case.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org