[jira] [Commented] (CAMEL-19100) Milo component does not use dataChangeFilterTrigger value from route

["Nicolas Filotto (Jira)" <ji...@apache.org>]

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

Nicolas Filotto commented on CAMEL-19100:
-----------------------------------------

Removing 4.0 from the fix versions since the milo component has been removed likely due to an incompatibility with the Jakarta migration.

> Milo component does not use dataChangeFilterTrigger value from route
> --------------------------------------------------------------------
>
>                 Key: CAMEL-19100
>                 URL: https://issues.apache.org/jira/browse/CAMEL-19100
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-milo
>    Affects Versions: 3.20.2, 3.x
>            Reporter: Gunnar Rangøy
>            Priority: Major
>             Fix For: 3.20.3, 3.21.0, 4.0-M2, 4.0
>
>         Attachments: filter.patch
>
>
> The dataChangeFilterTrigger configured is not applied when the monitoring is set up.
>  
>  
> {code:java}
> return new DataChangeFilter(
>    DataChangeTrigger.StatusValueTimestamp,
>    this.getDataChangeFilterDeadbandType(),
>    this.getDataChangeFilterDeadbandValue());
> }{code}
> I think the code above has to be changed to something like this:
>   
> {code:java}
> return new DataChangeFilter(
> this.dataChangeFilterTrigger != null ? this.dataChangeFilterTrigger : DataChangeTrigger.StatusValueTimestamp,
> this.getDataChangeFilterDeadbandType(),
> this.getDataChangeFilterDeadbandValue());
> }{code}



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