[ 
https://issues.apache.org/jira/browse/ARTEMIS-4653?focusedWorklogId=906111&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-906111
 ]

ASF GitHub Bot logged work on ARTEMIS-4653:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 20/Feb/24 23:34
            Start Date: 20/Feb/24 23:34
    Worklog Time Spent: 10m 
      Work Description: tabish121 opened a new pull request, #4829:
URL: https://github.com/apache/activemq-artemis/pull/4829

   …filters
   
   When Queue consumers attach with filters use those instead of the Queue 
filter to filter the messages that are federated to avoid stranding of messages 
on the local broker. This will result in multiple federation consumers if the 
various attached local consumers all use different filters but does keop 
unwanted messages on the remote so that consumers there can consume those.




Issue Time Tracking
-------------------

            Worklog Id:     (was: 906111)
    Remaining Estimate: 0h
            Time Spent: 10m

> AMQP Federation should apply queue consumer filters for demand
> --------------------------------------------------------------
>
>                 Key: ARTEMIS-4653
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4653
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: AMQP
>    Affects Versions: 2.32.0
>            Reporter: Timothy A. Bish
>            Assignee: Timothy A. Bish
>            Priority: Minor
>             Fix For: 2.33.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> For Queue federation the federation consumers should apply a consumer defined 
> filter over the Queue defined filter to avoid pulling message across the link 
> that won't be deliverable.  Add options for disabling this and also disabling 
> per consumer consumer priority tracking to allow for reduction of federation 
> links when desired.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to