You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/09/22 10:27:00 UTC
[jira] [Updated] (FLINK-40743) JDBC Table sink reports an empty lineage dataset name
[ https://issues.apache.org/jira/browse/FLINK-40743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-40743:
-----------------------------------
Labels: pull-request-available (was: )
> JDBC Table sink reports an empty lineage dataset name
> -----------------------------------------------------
>
> Key: FLINK-40743
> URL: https://issues.apache.org/jira/browse/FLINK-40743
> Project: Flink
> Issue Type: Bug
> Components: Connectors / JDBC
> Affects Versions: jdbc-4.0.0, jdbc-4.1.0
> Reporter: Martijn Visser
> Assignee: Martijn Visser
> Priority: Major
> Labels: pull-request-available
> Fix For: jdbc-5.0.0
>
>
> `TableLineageUtils.extractLineageDataset` runs at plan time on the object `SinkFunctionProvider.createSinkFunction()` returns. `JdbcOutputFormat.getLineageVertex()` reads the statement text from the transient statement executor, which only exists after `open()`, so the dataset name is always `""` for Table sinks (the DataStream `JdbcSink` is fine).
> Fix: give the format the dialect's INSERT statement at build time. See also FLINK-39935 (planner-side override of the dataset name; independent).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)