[
https://issues.apache.org/jira/browse/BAHIR-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16865560#comment-16865560
]
ASF GitHub Bot commented on BAHIR-183:
--------------------------------------
yanlin-Lynn commented on issue #84: [BAHIR-183] [WIP] HDFS based MQTT client
persistence
URL: https://github.com/apache/bahir/pull/84#issuecomment-502665465
> @lresende, I would answer positive. This PR changes the way we implement
HDFS persistence due to issues pointed out in [JIRA
commant](https://issues.apache.org/jira/browse/BAHIR-183?focusedCommentId=16800091&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16800091).
> @yanlin-Lynn, can you also have a look since I changed mostly the code you
have introduced and worked on previously?
Very sorry to keep you wait. I will review it in weekends.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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
> Assignee: Wang Yanlin
> Priority: Major
> Fix For: Spark-2.4.0
>
>
> 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)
