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

Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2023/08/11 10:36:00 UTC

[jira] [Updated] (FLINK-31332) Limit the use of ExecutionConfig on JdbcOutputFormat

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

Flink Jira Bot updated FLINK-31332:
-----------------------------------
    Labels: pull-request-available stale-major  (was: pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> Limit the use of ExecutionConfig on JdbcOutputFormat
> ----------------------------------------------------
>
>                 Key: FLINK-31332
>                 URL: https://issues.apache.org/jira/browse/FLINK-31332
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: João Boto
>            Priority: Major
>              Labels: pull-request-available, stale-major
>
> This is for limiting the use of ExecutionConfig on JdbcOutputFormat and centralize the logic of serialisation of records in one place.
> Also current the record will be copied at least 2/3 times if isObjectReuse is enabled



--
This message was sent by Atlassian Jira
(v8.20.10#820010)