You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2021/07/30 10:26:00 UTC

[jira] [Resolved] (CAMEL-16800) camel-core - Re-introduce the FILTER_MATCHED logic in FilterProcessor

     [ https://issues.apache.org/jira/browse/CAMEL-16800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-16800.
---------------------------------
    Resolution: Won't Fix

Its a core optimization that adds some unnessary overhead 

> camel-core - Re-introduce the FILTER_MATCHED logic in FilterProcessor
> ---------------------------------------------------------------------
>
>                 Key: CAMEL-16800
>                 URL: https://issues.apache.org/jira/browse/CAMEL-16800
>             Project: Camel
>          Issue Type: Wish
>          Components: camel-core
>    Affects Versions: 3.9.0, 3.10.0, 3.11.0
>            Reporter: Tom Cassimon
>            Priority: Major
>
> We use this property to check after a part of the route is done if the filter specified in that part of the route has a match or not. It would be handy to re-introduce this as now we need to implement custom logic to achieve this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)