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

Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2021/09/26 15:58:00 UTC

[jira] [Resolved] (KARAF-7257) Make the inclusion of camel history configurable

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

Jean-Baptiste Onofré resolved KARAF-7257.
-----------------------------------------
    Fix Version/s: decanter-2.9.0
       Resolution: Fixed

> Make the inclusion of camel history configurable
> ------------------------------------------------
>
>                 Key: KARAF-7257
>                 URL: https://issues.apache.org/jira/browse/KARAF-7257
>             Project: Karaf
>          Issue Type: New Feature
>          Components: decanter
>    Affects Versions: decanter-2.8.0
>            Reporter: Oliver Wulff
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: decanter-2.9.0
>
>
> The history within the event can cause a lot of unstructed data. Every history item is added at the top level with other fields like properties, inHeaders, ...
> History should be written to the field "history".
> It can be configured whether history should be written or not like properties, headers and body.



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