[
https://issues.apache.org/jira/browse/BAHIR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282940#comment-16282940
]
ASF GitHub Bot commented on BAHIR-104:
--------------------------------------
Github user ckadner commented on the issue:
https://github.com/apache/bahir/pull/55
**LGTM**
I ran the (new) Python tests manually and they completed successfully.
**Before:**
```
[bahir] (master *=)$ streaming-mqtt/python-tests/run-python-tests.sh
----------------------------------------------------------------------
Ran 1 test in 22.871s
OK
```
**After:**
```
[bahir] (pr-55_BAHIR-104_python_pairRDD *=)$
streaming-mqtt/python-tests/run-python-tests.sh
----------------------------------------------------------------------
Ran 2 tests in 27.593s
OK
```
> MQTT Dstream returned by the new multi topic support API is not a pairRDD
> -------------------------------------------------------------------------
>
> Key: BAHIR-104
> URL: https://issues.apache.org/jira/browse/BAHIR-104
> Project: Bahir
> Issue Type: Bug
> Components: Spark Streaming Connectors
> Affects Versions: Spark-2.1.0
> Reporter: Francesco Beneventi
> Labels: MQTT, SPARK
>
> The new multi topic support API added with [BAHIR-89], when used in pyspark,
> does not return a Dstream of <topic,message> tuples.
> Example:
> In pyspark, when creating a Dstream using the new API ( mqttstream =
> MQTTUtils.createPairedStream(ssc, brokerUrl, topics) ) the expected contents
> of mqttstream should be a collections of tuples:
> (topic,message) , (topic,message) , (topic,message) , ...
> Instead, the current content is a flattened list:
> topic, message, topic, message, topic, message, ...
> that is hard to use.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
