[
https://issues.apache.org/jira/browse/NIFI-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373362#comment-15373362
]
Joseph Witt commented on NIFI-2164:
-----------------------------------
In my opinion such a distinction is leaky. The repositories upon commit should
be considered as having written the data from a caller/api point of view. That
specific implementations might have to consider os caches and disk buffering
should be a concern local to that repository. Generally speaking people tend
not to run at true 'always sync' mode due to its prohibitive overhead but this
is an option.
> ConsumeJMS should allow user to configure trade-off between 'best effort' and
> 'guaranteed receipt' of data
> ----------------------------------------------------------------------------------------------------------
>
> Key: NIFI-2164
> URL: https://issues.apache.org/jira/browse/NIFI-2164
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Oleg Zhurakousky
>
> Currently the ConsumeJMS Processor uses auto-acknowledge acknowledgement.
> This is beneficial for many use cases but could result in data loss if NiFi
> is shut down. We should expose a 'Delivery Guarantee' property that allows
> the user to choose between 'Best Effort', which will provide better
> performance or 'Guaranteed Receipt', which will guarantee that data has been
> committed to NiFi's Content & FlowFile Repositories before acknowledging the
> message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
