[
https://issues.apache.org/jira/browse/NIFI-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364607#comment-15364607
]
Joey Frazee commented on NIFI-2164:
-----------------------------------
I think exposing the version of FlowFileRepository.updateRepository() that has
a sync parameter in its signature [1] to ProcessSession.commit() [2] will make
this doable as well as being useable for processors besides ConsumeJMS.
Thoughts?
1.
https://github.com/apache/nifi/blob/32b8a9b9f4c07b4f5d3049c33880b547481cbb24/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/repository/WriteAheadFlowFileRepository.java#L193
2.
https://github.com/apache/nifi/blob/470513fa2ec10dbc328b80b8b72f88f1539e523c/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/repository/StandardProcessSession.java#L298
> 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
> Fix For: 1.0.0
>
>
> 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)
