[
https://issues.apache.org/jira/browse/ARTEMIS-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652648#comment-16652648
]
ASF GitHub Bot commented on ARTEMIS-2117:
-----------------------------------------
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2362
@clebertsuconic if you could share, im a bit surprised its this, as the new
features should only impact if enabled, so wan't expecting any issues in old
cases. Obviously like always happy to look at, as something could have been
overlooked
> Add QPID LVQ Features into Broker
> ---------------------------------
>
> Key: ARTEMIS-2117
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2117
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.6.3
> Reporter: Michael Andre Pearce
> Assignee: Michael Andre Pearce
> Priority: Major
>
> To assist users migrating from qpid to artemis.
> Currently LVQ in artemis uses a fixed message property for the LVQ key, Qpid
> supports queues to have custom/arbitrary message property to be the LVQ key,
> this is more flexible.
> [http://qpid.apache.org/releases/qpid-broker-j-7.0.1/book/Java-Broker-Concepts-Queues.html#Java-Broker-Concepts-Queues-Types-LVQ]
>
> Also an additional feature typically used with LVQ's in qpid is ability to
> mark a queue non-destructive.
> [http://qpid.apache.org/releases/qpid-broker-j-7.0.1/book/Java-Broker-Concepts-Queues.html#Java-Broker-Concepts-Queue-EnsureNonDestructiveConsumers]
>
> As such this is to add both support ability to use a arbitrary last-value-key
> for LVQ and for support of setting a queue to be non-destructive, at the
> broker level and via core apis.
> Scope is to add basic feature into the broker and core apis, out of scope is
> dynamic creation from a client via amqp which would be a later piece of work.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
