[PR] [FLINK-39810][Kinesis/Connector] Add lineage support to Kinesis Streams connector [flink-connector-aws]

["fmorillo7694 (via GitHub)" <gi...@apache.org>]

fmorillo7694 opened a new pull request, #250:
URL: https://github.com/apache/flink-connector-aws/pull/250

   Implements LineageVertexProvider interface on KinesisStreamsSource and KinesisStreamsSink to enable automatic lineage extraction in Flink 2.x.
   
   The LineageGraph API in Flink 2.0+ allows the table planner and OpenLineage integration to automatically discover input/output datasets with their metadata. This change enables lineage for both DataStream and SQL/Table API usage of the Kinesis connector.
   
   New classes:
   - KinesisLineageUtil: namespace/name extraction from stream ARN
   - KinesisDatasetFacet: stream ARN, name, region metadata
   - TypeDatasetFacet: schema information via TypeInformation
   
   Namespace format uses full ARN prefix for governance specificity:
     arn:{partition}:kinesis:{region}:{account}:stream
   
   Dataset name is the stream name extracted from the ARN.
   
   Covers DataStream API (direct), SQL/Table API (via KinesisDynamicSource which internally creates KinesisStreamsSource), and the sink path.
   
   <!--
   *Thank you for contributing to Apache Flink AWS Connectors - we are happy that you want to help us improve our Flink connectors. 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.*
   
   ## Contribution Checklist
   
   - The name of the pull request should correspond 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.
   - Commits should be in the form of "[FLINK-XXXX][component] Title of the pull request", where [FLINK-XXXX] should be replaced by the actual issue number. 
       Generally, [component] should be the connector you are working on.
       For example: "[FLINK-XXXX][Connectors/Kinesis] XXXX" if you are working on the Kinesis connector or "[FLINK-XXXX][Connectors/AWS] XXXX" if you are working on components shared among all the connectors.
   - Each pull request should only have one JIRA issue.
   - Once all items of the checklist are addressed, remove the above text and this checklist, leaving only the filled out template below.
   -->
   
   ## Purpose of the change
   
   *For example: Implements the Table API for the Kinesis Source.*
   
   ## Verifying this change
   
   Please make sure both new and modified tests in this PR follows the conventions defined in our code quality guide: https://flink.apache.org/contributing/code-style-and-quality-common.html#testing
   
   *(Please pick either of the following options)*
   
   This change is a trivial rework / code cleanup without any test coverage.
   
   *(or)*
   
   This change is already covered by existing tests, such as *(please describe tests)*.
   
   *(or)*
   
   This change added tests and can be verified as follows:
   
   *(example:)*
   - *Added integration tests for end-to-end deployment*
   - *Added unit tests*
   - *Manually verified by running the Kinesis connector on a local Flink cluster.*
   
   ## Significant changes
   *(Please check any boxes [x] if the answer is "yes". You can first publish the PR and check them afterwards, for convenience.)*
   - [ ] Dependencies have been added or upgraded
   - [ ] Public API has been changed (Public API is any class annotated with `@Public(Evolving)`)
   - [ ] Serializers have been changed
   - [ ] New feature has been introduced
     - If yes, how is this documented? (not applicable / docs / JavaDocs / not documented)
   


-- 
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

Re: [PR] [FLINK-39813][Connectors/Kinesis] Add lineage support to Kinesis Streams connector [flink-connector-aws]

["fmorillo7694 (via GitHub)" <gi...@apache.org>]

fmorillo7694 commented on PR #250:
URL: https://github.com/apache/flink-connector-aws/pull/250#issuecomment-5476537782

   The OpenLineage-side counterpart of this PR — [OpenLineage/OpenLineage#4861](https://github.com/OpenLineage/OpenLineage/pull/4861) (Kinesis dataset visitors consuming the facets introduced here) — has been approved by the OpenLineage maintainer.
   
   This validates the dataset naming convention (`arn:{partition}:kinesis:{region}:{account}` / `stream/{streamName}`) and the facet contract on both sides of the integration. This PR remains rebased on main, CI green, and ready for committer review.
   


-- 
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