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

Posted to issues@karaf.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2016/02/01 15:41:40 UTC

[jira] [Updated] (KARAF-4303) Create decanter marshalling services

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

Christian Schneider updated KARAF-4303:
---------------------------------------
    Affects Version/s: decanter-1.0.1

> Create decanter marshalling services
> ------------------------------------
>
>                 Key: KARAF-4303
>                 URL: https://issues.apache.org/jira/browse/KARAF-4303
>             Project: Karaf
>          Issue Type: New Feature
>          Components: decanter
>    Affects Versions: decanter-1.0.1
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Christian Schneider
>
> The decanter collectors collect the data as a key/value pair data (Map).
> The decanter appenders directly uses this Map to store on the backend (it's the case for Camel and ActiveMQ appenders), but other appenders marshall this Map as a JSON string (it's the case of the Elasticsearch or JDBC appenders).
> As a good design improvement, we can provide a DecanterMarshaller interface that convert this Map as a Object. We can implement a first JSONDecanterMarshaller service (we can imagine to provide new marshallers later). The appenders can "filter" to pick the marshaller he wants to use or just use one service (when multiple).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)