[ 
https://issues.apache.org/jira/browse/NIFI-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Turcsanyi updated NIFI-10500:
-----------------------------------
    Status: Patch Available  (was: Open)

> Improve property ordering in MQTT processors
> --------------------------------------------
>
>                 Key: NIFI-10500
>                 URL: https://issues.apache.org/jira/browse/NIFI-10500
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Peter Turcsanyi
>            Assignee: Peter Turcsanyi
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> MQTT processors have evolved over time and new properties have been added not 
> in the optimal order. The abstract processor contained the list of common 
> properties for Consume and Publish processors and it led to a weird ordering 
> because some common properties with low importance precede other more 
> important ones (but specific to only Consume or Publish).
> Do a generic facelift on the processors regarding the property ordering.
> *PublishMQTT:*
> Broker URI
> MQTT Specification Version
> Username
> Password
> SSL Context Service
> Session State
> Session Expiry Interval
> Client ID
> Topic
> Retain Message
> Quality of Service (QoS)
> Connection Timeout (seconds)
> Keep Alive Interval (seconds)
> Last Will Message
> Last Will Topic => should depend on Last Will Message
> Last Will Retain => should depend on Last Will Message
> Last Will QoS Level => should depend on Last Will Message
> *ConsumeMQTT:*
> Broker URI
> MQTT Specification Version
> Username
> Password
> SSL Context Service
> Session State
> Session Expiry Interval
> Client ID
> Group ID
> Topic Filter
> Quality of Service (QoS)
> Max Queue Size
> Record Reader
> Record Writer
> Add Attributes as Fields
> Message Demarcator
> Connection Timeout (seconds)
> Keep Alive Interval (seconds)
> Last Will Message
> Last Will Topic => should depend on Last Will Message
> Last Will Retain => should depend on Last Will Message
> Last Will QoS Level => should depend on Last Will Message



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to