[
https://issues.apache.org/jira/browse/KARAF-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17420321#comment-17420321
]
ASF subversion and git services commented on KARAF-7257:
--------------------------------------------------------
Commit d33400fd3174ffda618d5d132e1c4d9ebdb4dbb4 in karaf-decanter's branch
refs/heads/main from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=karaf-decanter.git;h=d33400f ]
Merge pull request #270 from olwulff/KARAF-7257
[KARAF-7257] Make inclusion of history configurable
> 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
>
> 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)
