Though AMQP 0-10 does not specify any functionality around selectors, it offers an appropriate extension point via the arguments filed of message-subscribe. The qpid java broker already uses this to support server side selectors and qpidd should follow the same scheme.

Would this be implemented in a separate queue type? i.e. Would there be a selectable/selector queue? Perhaps there would be little overhead but it seems that we should make this a type of queue so that any overhead doesn't adversely effect more lightweight low-latency queues.

-> POST

From the point of view of downstream release preparation, this is ready, even though the upstream issue has some remaining tasks.

Please open new issues for any defects or improvements.

( 1 ) Does the Identifiers that starts with $ or _ have some special meaning ?

( 2 ) Should the grammar really allow identifiers like $, $$, $$$, _, __, _$_, _.__.., $., a etc.?

( 3 ) Could you provide (if any exists) some special examples ? for example usage of variables, or some build in functions/macros like "amqp.timestamp - time.timestamp() < 5" is such exists

(In reply to Zdenek Kraus from comment #19)
> ( 1 ) Does the Identifiers that starts with $ or _ have some special meaning
> ?
> 
> ( 2 ) Should the grammar really allow identifiers like $, $$, $$$, _, __,
> _$_, _.__.., $., a etc.?
> 
> ( 3 ) Could you provide (if any exists) some special examples ? for example
> usage of variables, or some build in functions/macros like "amqp.timestamp -
> time.timestamp() < 5" is such exists

See comment #14 - This is really a tracker bug for the overall feature, please open a new BZ for issues.

I haven't reported you any new issue, I just wanted to ask you 3 simple questions, and for that I won't open a new issue, so please if you could answer me.

Summary: all code related blocking issues are in VERIFIED, waiting for DOC

DOC resolved -> VERIFIED

Adding reference to the docs in the release note text so customer know where to read more about the feature.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-1296.html