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 2017/08/09 06:51:00 UTC
[jira] [Resolved] (SPARK-21596) Audit the places calling
HDFSMetadataLog.get
[ https://issues.apache.org/jira/browse/SPARK-21596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shixiong Zhu resolved SPARK-21596.
----------------------------------
Resolution: Fixed
Assignee: Shixiong Zhu
Fix Version/s: 2.3.0
2.2.1
> Audit the places calling HDFSMetadataLog.get
> --------------------------------------------
>
> Key: SPARK-21596
> URL: https://issues.apache.org/jira/browse/SPARK-21596
> Project: Spark
> Issue Type: Bug
> Components: Structured Streaming
> Affects Versions: 2.1.1
> Reporter: Shixiong Zhu
> Assignee: Shixiong Zhu
> Fix For: 2.2.1, 2.3.0
>
>
> When I was investigating a flaky test, I realized that many places don't check the return value of `HDFSMetadataLog.get(batchId: Long): Option[T]`. When a batch is supposed to be there, the caller just ignores None rather than throwing an error. If some bug causes a query doesn't generate a batch metadata file, this behavior will hide it and allow the query continuing to run.
--
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