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 2023/02/28 13:00:00 UTC
[jira] [Commented] (CAMEL-19100) Milo component does not use dataChangeFilterTrigger value from route
[ https://issues.apache.org/jira/browse/CAMEL-19100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694522#comment-17694522 ]
Claus Ibsen commented on CAMEL-19100:
-------------------------------------
Thanks for reporting and the patch.
> 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
>
> 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)