[jira] [Commented] (NIFI-2663) Add Websocket support for MQTT protocol

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on NIFI-2663:
--------------------------------------

GitHub user SebastianCarroll opened a pull request:

    https://github.com/apache/nifi/pull/2154

    NIFI-2663: Add WebSocket support for MQTT processors

    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [x] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    - [x] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
    - [ ] Have you written or updated unit tests to verify your changes?
    - [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [x] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
    - [x] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
    - [x] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [x] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/SebastianCarroll/nifi NIFI-2663

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/2154.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 #2154
    
----
commit 4f6184f966fd19b2d892f43417f42635107a1da7
Author: Sebastian Carroll <sc...@hortonworks.com>
Date:   2017-09-13T15:21:56Z

    NIFI-2663: Add WebSocket support for MQTT processors

----


> Add Websocket support for MQTT protocol
> ---------------------------------------
>
>                 Key: NIFI-2663
>                 URL: https://issues.apache.org/jira/browse/NIFI-2663
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 1.0.0, 0.7.0, 0.6.1
>            Reporter: Andrew Psaltis
>            Assignee: Andrew Psaltis
>
> Today NiFi only supports MQTT over plain TCP using the PublishMQTT and ConsumeMQTT processors. However, there are many cases in the IoT world where WebSockets (secure and not) is the preferred transport mechanism for MQTT.  This JIRA is to enhance those processors to also support WS.
> Following are the basics of what is required:
>  
> 1)      Require to configure web socket as the transport protocol, currently PublishMQTT processor supports TCP as the only transport protocol
> 2)      URL input for the Web socket transport should be in the format of ws://IPAddress:websocket_listening_port, as of now it accepts only TCP url, and a bulletin is raised if a protocol other than tcp or ssl is used.
> 3)      Similar to TCP non-secured and secured publisher we should extend/provide processor to support WS and WSS transport protocols



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)