[
https://issues.apache.org/jira/browse/BAHIR-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16706075#comment-16706075
]
ASF GitHub Bot commented on BAHIR-183:
--------------------------------------
GitHub user yanlin-Lynn opened a pull request:
https://github.com/apache/bahir/pull/72
[BAHIR-183]Using HDFS for saving message for mqtt source.
Currently in spark-sql-streaming-mqtt, the received mqtt message is saved
in a local file by driver, this will have the risks of losing data for cluster
mode when application master failover occurs. So add a hdfs-based mqtt source
to solve this problem.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yanlin-Lynn/bahir bahir-183
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/bahir/pull/72.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #72
----
commit eb33741f8b77828815c8f834ec0951d6c39728fc
Author: wangyanlin01 <wangyanlin01@...>
Date: 2018-12-02T03:00:21Z
[BAHIR-183]Using HDFS for saving message for mqtt source.
----
> Using HDFS for saving message for mqtt source
> ---------------------------------------------
>
> Key: BAHIR-183
> URL: https://issues.apache.org/jira/browse/BAHIR-183
> Project: Bahir
> Issue Type: Improvement
> Components: Spark Structured Streaming Connectors
> Affects Versions: Spark-2.2.0
> Reporter: Wang Yanlin
> Priority: Major
> Fix For: Spark-2.2.1
>
>
> Currently in spark-sql-streaming-mqtt, the received mqtt message is saved in
> a local file by driver, this will have the risks of losing data for cluster
> mode when application master failover occurs. So saving in-coming mqtt
> messages using a director in checkpoint will solve this problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
