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

Posted to issues@flink.apache.org by "Martin Eden (JIRA)" <ji...@apache.org> on 2018/12/21 01:54:00 UTC

[jira] [Commented] (FLINK-7689) Instrument the Flink JDBC sink

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

Martin Eden commented on FLINK-7689:
------------------------------------

This should ready for merging now!

> Instrument the Flink JDBC sink
> ------------------------------
>
>                 Key: FLINK-7689
>                 URL: https://issues.apache.org/jira/browse/FLINK-7689
>             Project: Flink
>          Issue Type: Improvement
>          Components: Streaming Connectors
>    Affects Versions: 1.4.0
>            Reporter: Martin Eden
>            Priority: Minor
>              Labels: jdbc, metrics
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> As confirmed by the Flink community in the following mailing list [message|http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/metrics-for-Flink-sinks-td15200.html]  using off the shelf Flink sinks like the JDBC sink, Redis sink or Cassandra sink etc does not expose any sink specific metrics.
> The purpose of this ticket is to add some relevant metrics to the JDBCOutputFormat:
> - Meters for when a flush is made.
> - Histograms for the jdbc batch count and batch execution latency.
> These would allow deeper understanding of the runtime behaviour of performance critical jobs writing to external databases using this generic interface.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)