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

Posted to issues@flink.apache.org by "jsingh-yelp (via GitHub)" <gi...@apache.org> on 2026/06/15 04:34:51 UTC

[PR] [FLINK-39219] [table] Allow connectors to override lineage dataset name [flink]

jsingh-yelp opened a new pull request, #28439:
URL: https://github.com/apache/flink/pull/28439

<!--
*Thank you very much for contributing to Apache Flink - we are happy that you want to help us improve Flink. To help the community review your contribution in the best possible way, please go through the checklist below, which will get the contribution into a shape in which it can be best reviewed.*

*Please understand that we do not do this to make contributions to Flink a hassle. In order to uphold a high standard of quality for code contributions, while at the same time managing a large number of contributions, we need contributors to prepare the contributions well, and give reviewers enough contextual information for the review. Please also understand that contributions that do not follow this guide will take longer to review and thus typically be picked up with lower priority by the community.*

## Contribution Checklist

- Make sure that the pull request corresponds to a [JIRA issue](https://issues.apache.org/jira/projects/FLINK/issues). Exceptions are made for typos in JavaDoc or documentation files, which need no JIRA issue.

- Name the pull request in the form "[FLINK-XXXX] [component] Title of the pull request", where *FLINK-XXXX* should be replaced by the actual issue number. Skip *component* if you are unsure about which is the best component.
Typo fixes that have no associated JIRA issue should be named following this pattern: `[hotfix] [docs] Fix typo in event time introduction` or `[hotfix] [javadocs] Expand JavaDoc for PuncuatedWatermarkGenerator`.

- Fill out the template below to describe the changes contributed by the pull request. That will give reviewers the context they need to do the review.

- Make sure that the change passes the automated tests, i.e., `mvn clean verify` passes. You can set up Azure Pipelines CI to do that following [this guide](https://cwiki.apache.org/confluence/display/FLINK/Azure+Pipelines#AzurePipelines-Tutorial:SettingupAzurePipelinesforaforkoftheFlinkrepository).

- Each pull request should address only one issue, not mix up code from multiple issues.

- Each commit in the pull request has a meaningful commit message (including the JIRA id)

- Once all items of the checklist are addressed, remove the above text and this checklist, leaving only the filled out template below.

**(The sections below can be removed for hotfixes of typos)**
-->

## What is the purpose of the change
Previously, `TableLineageDatasetImpl` always used the Flink catalog identifier (contextResolvedTable.getIdentifier().asSummaryString()) as the dataset name. Now it prefers the name provided by the connector's LineageDataset when available, enabling connectors like Paimon to use more stable identifiers (e.g., JDBC catalog-key instead of the logical catalog name registered in Flink).

## Brief change log
- `TableLineageDatasetImpl` now uses the connector-provided `LineageDataset.name()` when present, falling back to the Flink identifier. This is consistent with how `namespace` is already handled in the same class.
- Added a test to verify the connector name override behavior.

## Verifying this change
- Added `testCreateTableLineageDatasetWithConnectorNameOverride` in `TableLineageUtilsTest` which verifies that when a connector provides a `LineageDataset` with a custom name, `TableLineageDatasetImpl.name()` uses the connector-provided name while `catalogContext` still reflects the Flink catalog.
- Existing tests (`testCreateTableLineageDatasetWithCatalog`, `testCreateTableLineageDatasetWithoutCatalog`) verify the fallback path when no connector lineage is provided.

## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with @Public(Evolving): no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
- The S3 file system connector: no

## Documentation
- Does this pull request introduce a new feature? ( no)
- If yes, how is the feature documented? (not applicable)

---

##### Was generative AI tooling used to co-author this PR?
No

--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org