spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shixiong Zhu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-21667) ConsoleSink should not fail streaming query with checkpointLocation option
Date Wed, 09 Aug 2017 18:35:00 GMT

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

Shixiong Zhu commented on SPARK-21667:
--------------------------------------

Do you mind to submit a PR to fix it?

> ConsoleSink should not fail streaming query with checkpointLocation option
> --------------------------------------------------------------------------
>
>                 Key: SPARK-21667
>                 URL: https://issues.apache.org/jira/browse/SPARK-21667
>             Project: Spark
>          Issue Type: Improvement
>          Components: Structured Streaming
>    Affects Versions: 2.3.0
>            Reporter: Jacek Laskowski
>            Priority: Minor
>
> As agreed on the Spark users mailing list in the thread "\[SS] Console sink not supporting
recovering from checkpoint location? Why?" in which [~marmbrus] said:
> {quote}
> I think there is really no good reason for this limitation.
> {quote}
> Using {{ConsoleSink}} should therefore not fail a streaming query when used with {{checkpointLocation}}
option.
> {code}
> // today's build from the master
> scala> spark.version
> res8: String = 2.3.0-SNAPSHOT
> scala> val q = records.
>      |   writeStream.
>      |   format("console").
>      |   option("truncate", false).
>      |   option("checkpointLocation", "/tmp/checkpoint"). // <--
> checkpoint directory
>      |   trigger(Trigger.ProcessingTime(10.seconds)).
>      |   outputMode(OutputMode.Update).
>      |   start
> org.apache.spark.sql.AnalysisException: This query does not support recovering from checkpoint
location. Delete /tmp/checkpoint/offsets to start over.;
>   at org.apache.spark.sql.streaming.StreamingQueryManager.createQuery(StreamingQueryManager.scala:222)
>   at org.apache.spark.sql.streaming.StreamingQueryManager.startQuery(StreamingQueryManager.scala:278)
>   at org.apache.spark.sql.streaming.DataStreamWriter.start(DataStreamWriter.scala:284)
>   ... 61 elided
> {code}
> The "trigger" is SPARK-16116 and [this line|https://github.com/apache/spark/pull/13817/files#diff-d35e8fce09686073f81de598ed657de7R277]
in particular.
> This also relates to SPARK-19768 that was resolved as not a bug.



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


Mime
View raw message