[ 
https://issues.apache.org/jira/browse/ARTEMIS-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375731#comment-15375731
 ] 

ASF GitHub Bot commented on ARTEMIS-573:
----------------------------------------

GitHub user jbertram opened a pull request:

    https://github.com/apache/activemq-artemis/pull/633

    ARTEMIS-573 clarify filter documentation

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-573

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/633.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #633
    
----
commit 9e107f0affd9a49a2eb39cdef24b1257b3fbcd27
Author: jbertram <jbert...@apache.org>
Date:   2016-07-13T20:47:24Z

    ARTEMIS-573 clarify filter documentation

----


> Please document the selector support
> ------------------------------------
>
>                 Key: ARTEMIS-573
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-573
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>    Affects Versions: 1.3.0
>            Reporter: Lionel Cons
>            Assignee: Justin Bertram
>
> SQL-like selectors used in subscriptions seem to be supported but they are 
> not documented. They are mentioned in several pages (including the 
> "Examples") page but not really documented.
> Idem for their STOMP support. Looking at the code I found out that a 
> {{selector}} header can be used in a {{SUBSCRIBE}} frame.
> It is very important to document the syntax supported by Artemis. From 
> memory, a selector like "foo-bar = 1" is supported in Apollo but not in 
> ActiveMQ 5.x. My tests indicate that Artemis does not support it either but, 
> the syntax being undocumented, I don't know if this is a bug or a feature...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to