Github user mosermw commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1036#discussion_r81410549
--- Diff:
nifi-nar-bundles/nifi-jms-bundle/nifi-jms-processors/src/main/java/org/apache/nifi/jms/processors/ConsumeJMS.java
---
@@ -54,8 +61,31 @@
@SeeAlso(value = { PublishJMS.class, JMSConnectionFactoryProvider.class })
public class ConsumeJMS extends AbstractJMSProcessor<JMSConsumer> {
+ static final AllowableValue AUTO_ACK = new
AllowableValue(String.valueOf(Session.AUTO_ACKNOWLEDGE),
+ "AUTO_ACKNOWLEDGE",
+ "Automatically acknowledges a client's receipt of a message,
regardless if NiFi session has been commited. "
+ + "Can result in data loss in the event where NiFi
abruptly stopped before session was commited.");
+
+ static final AllowableValue CLIENT_ACK = new
AllowableValue(String.valueOf(Session.CLIENT_ACKNOWLEDGE),
+ "CLIENT_ACKNOWLEDGE",
+ "(DEFAULT) Manually acknowledges a client's receipt of a
message after NiFi Session was commited, thus ensuring no data loss");
+
+ static final AllowableValue DUPS_OK = new
AllowableValue(String.valueOf(Session.DUPS_OK_ACKNOWLEDGE),
+ "DUPS_OK_ACKNOWLEDGE",
+ "This acknowledgment mode instructs the session to lazily
acknowledge the delivery of messages. May result uin both data "
--- End diff --
Spelling "uin"
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
