karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-4303) Create decanter marshalling services
Date Tue, 02 Feb 2016 16:41:39 GMT

    [ https://issues.apache.org/jira/browse/KARAF-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15128511#comment-15128511

ASF subversion and git services commented on KARAF-4303:

Commit 9e0a2215d2556c934c829ac9dc7ce3efdb645e81 in karaf-decanter's branch refs/heads/master
from [~chris@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=9e0a221 ]

[KARAF-4303] Use marshaller in jdbc appender and refactor

> 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
>             Fix For: decanter-1.0.2
> 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

View raw message