Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/1521
**JPercivall**
The more I type out and try to easily distinguish GetAWSIoT/PutAWSIoT and
GetAWSIoTShadow/PutAWSIoTShadow the more I think MQTT should be integrated into
the name and all four of the processors should be Publish/Consume.
The GetAWSIoT and PutAWSIoT don't support all the AWS IoT protocols (don't
support "HTTP") and only support MQTT and MQTT over websockets. The name should
convey that they are specifically MQTT processors.
In NiFi, we have a couple different naming conventions. Get/Put are for
processors that do individual requests to some endpoint. For example GetFile
and PutFile, they don't have any lasting connections and each time get or put a
file. Publish and Consume, in general, are for processors which are
listening/putting to a topic. For example the PublishKafka and ConsumeKafka
processors publish and subscribe to a Kafka topic (it's "consume" instead
"subscribe" because we're actually doing something with the messages and not
just "subscribing" to a topic, there was a whole big thread about it).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
