[
https://issues.apache.org/jira/browse/ARTEMIS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15723016#comment-15723016
]
Timothy Bish commented on ARTEMIS-869:
--------------------------------------
Keep in mind though that if someone who tests such spec compliance adherence
might very well write or run an existing compliance suite of sorts that checks
these things and this change would be a valid violation of the JMS spec in
these tests that may or may not exist.
> Extend DeliveryMode to add a "LAZY_PERSISTENCE" option
> ------------------------------------------------------
>
> Key: ARTEMIS-869
> URL: https://issues.apache.org/jira/browse/ARTEMIS-869
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Reporter: Matt Pavlovich
>
> Currently the JMS Spec defines two delivery modes-- NON_PERSISTENT and
> PERSISTENT. Similar to how the ACK modes have been extended, it would be
> handy to extend the DeliveryMode to support a Kafka-like use case where the
> message should be persisted, but not require a sync() before being ack'd.
> Currently, the only way to define this in ActiveMQ 5.x is the periodic option
> on KahaDB, which effects all messages. It would be handy to be able to also
> define it at the per-message level
> Ideas on option:
> ActiveMQDeliveryMode.LAZY_PERSISTENCE
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
