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

ASF GitHub Bot commented on BAHIR-104:
--------------------------------------

Github user ckadner commented on the issue:

    https://github.com/apache/bahir/pull/55
  
    The problem is that one failing test in `sql-cloudant` causes all remaining 
tests to be skipped. Which means this PR can't be tested.
    
    @emlaver -- If you had an actual fix, could you create a PR for which we 
can quickly merge? Then this PR could be rebased on that latest code.
    
    If that is not possible, I will have to look into changing the Jenkins 
build to run the tests separately from (and after) the compile/package build 
and tell Maven to keep running after test failures.


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

Reply via email to