Bug 707628 - LVQ behaviour enhancement needs to be documented
Summary: LVQ behaviour enhancement needs to be documented
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Messaging_Programming_Reference
Version: Development
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: 2.2
: ---
Assignee: Joshua Wulf
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-25 14:50 UTC by Petr Matousek
Modified: 2018-11-26 17:35 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-20 03:13:27 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Petr Matousek 2011-05-25 14:50:20 UTC
Description of problem:
[RFE] qpid LVQ behaviour enhancement needs to be documented.
Please see Bug 632000

Version-Release number of selected component (if applicable):
MRG Messaging User Guide - Revision 0.1-6

How reproducible:
n/a

Steps to Reproduce:
1.
2.
3.
  
Actual results:
No documentation provided for LVQ behaviour enhancement.

Expected results:
LVQ behaviour enhancement documentation available.

Additional info:

Comment 1 Alison Young 2011-05-26 00:06:16 UTC
Insufficient time for inclusion in 2.0. 
RFE for 2.1, set 'requires_release_note' flag if a mention is required in the Release Notes for 2.0

Comment 3 Lana Brindley 2011-10-13 02:56:14 UTC
Setting NEEDINFO from reporter, please feel free to pass on to someone more appropriate.

Will be addressed after 2.1.

LKB

Comment 4 Petr Matousek 2011-10-13 09:43:35 UTC
Gordon Sim confirmed that he will provide some description of the new LVQ functionality. Please contact Gordon for informations needed. Some knowledge can be also gained from in Bug 632000.

Comment 5 Gordon Sim 2011-10-13 10:25:10 UTC
I'd replace the 'last value queues' section in chapter 3 with something like:

  Last value queues retain only the last message for each value of a
  particular message property. To enable this behaviour, choose the
  message property on which to key messages using the 
  qpid.last_value_queue_key argument when creating the queue.

  For example, lets assume a last value queue is created keyed on
  property 'ticker'. Messages can be sent with different values for
  the 'ticker' property. Only the last message for each ticker will
  be held in the queue.

  You can subscribe as a browser to such a queue in order to get the
  latest set of messages for all tickers, as well as any future
  updates. Providing all subscribers are browsing (and not dequeing
  messages), they can all share the same last value queue instance.

Of course the old behaviour as currently documented is still supported and if desired can be kept in in some form.

Comment 6 Ted Ross 2012-02-14 21:52:37 UTC
New content upstream related to this issue:

http://qpid.apache.org/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s06.html

Comment 14 Cheryn Tan 2012-09-20 02:54:12 UTC
Released for MRG 2.2


Note You need to log in before you can comment on or make changes to this bug.