[
https://issues.apache.org/jira/browse/BAHIR-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671378#comment-16671378
]
ASF GitHub Bot commented on BAHIR-181:
--------------------------------------
GitHub user ZisZ opened a pull request:
https://github.com/apache/bahir/pull/69
[BAHIR-181] username and password should be available for pyspark when
using mqtt streaming
When using spark-streaming-mqtt with pyspark to access rabbitmq, I found
there are no username and password provied for python api;
These two params are important and necessary for rabbitmq especially when
using rabbitmq virtual hosts, so I added a group of functions here;
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ZisZ/bahir master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/bahir/pull/69.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 #69
----
commit bea2aec58b7903c11907ba1d9687c48f90bb8519
Author: zhankeyu <zisz>
Date: 2018-11-01T09:26:19Z
add user and password in MQTTUtils for pyspark
commit 818acf8d1cd8ddd31a721126b49529b83dd3bfda
Author: zhankeyu <zisz>
Date: 2018-11-01T09:37:11Z
adjust code style
----
> username and password should be available for pyspark when using mqtt
> streaming
> -------------------------------------------------------------------------------
>
> Key: BAHIR-181
> URL: https://issues.apache.org/jira/browse/BAHIR-181
> Project: Bahir
> Issue Type: Improvement
> Components: Spark Streaming Connectors
> Affects Versions: Spark-2.3
> Environment: spark 2.3.1, python3.6
> Reporter: Carrey Zhan
> Priority: Minor
>
> When using spark-streaming-mqtt with pyspark to access rabbitmq, I found
> there are no username and password provied for python api;
> These two params are important and necessary for rabbitmq especially when
> using rabbitmq virtual hosts, so I added a group of functions here;
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)