Github user jtstorck commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2475#discussion_r168896206
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/PublishAMQP.java
---
@@ -62,6 +64,7 @@
+ "and Queue is not set up, the message will have no final
destination and will return (i.e., the data will not make it to the queue). If "
+ "that happens you will see a log in both app-log and bulletin
stating to that effect. Fixing the binding "
+ "(normally done by AMQP administrator) will resolve the issue.")
+@HighResourceUsageScenario(resource = SystemResource.MEMORY)
--- End diff --
The developer can provide a description using the "scenario" argument on
the annotation. This first pass was to identify most of the processors that
have the annotation. As we look through the list of components, specific
descriptions can be added to override the default scenario from the annotation
itself.
---
