[
https://issues.apache.org/jira/browse/KARAF-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419415#comment-17419415
]
ASF GitHub Bot commented on KARAF-7257:
---------------------------------------
olwulff opened a new pull request #270:
URL: https://github.com/apache/karaf-decanter/pull/270
- includeHistory propery makes inclusion of history configurable
- history stored as list within property "history" in the data object like
headers, etc.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> 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
> 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)
