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 2015/07/14 19:18:05 UTC

[jira] [Commented] (KARAF-3637) Decanter: JDBC appender

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

Jean-Baptiste Onofré commented on KARAF-3637:
---------------------------------------------

I refactored the JDBC appender. Especially there were some mistakes:
- the create SQL query was not working for all database
- it's not possible to use a PreparedStatement for a create
- the indexes of PreparedStatement were not right (PreparedStatement starts to count at 1 and not 0)
- previously the JDBC appender created one record per property in the consumed Event, whereas it should create one record per event (or use two tables, one for the event, and one for the properties in the event). For now, I use a single table containing one record per event, the event content is the JSON representation of the event. A possible enhancement would be to use two tables.

I tested in Karaf using a derby embedded datasource and it works fine.

> Decanter: JDBC appender
> -----------------------
>
>                 Key: KARAF-3637
>                 URL: https://issues.apache.org/jira/browse/KARAF-3637
>             Project: Karaf
>          Issue Type: New Feature
>          Components: decanter
>            Reporter: Morgan hautman
>            Assignee: Jean-Baptiste Onofré
>             Fix For: decanter-1.0.0
>
>




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