[
https://issues.apache.org/jira/browse/FLINK-40420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18107778#comment-18107778
]
Bettle commented on FLINK-40420:
--------------------------------
Hi ,I’m currently working on PyFlink-related issues and would also like to
contribute to the development of the new PyFlink DataFrame API.
I’d like to work on this issue. My proposed approach is:
* Add the six set-operation methods: {{{}union{}}}, {{{}union_all{}}},
{{{}intersect{}}}, {{{}intersect_all{}}}, {{{}minus{}}}, and {{{}minus_all{}}}.
* Delegate these operations to the corresponding Table API implementations
while preserving the existing validation behavior.
* Add focused tests covering duplicate-row semantics for the regular and
{{ALL}} variants, invalid inputs, and incompatible schemas.
* Update the DataFrame API documentation accordingly.
Could you please confirm whether this approach fits the intended DataFrame API
design and assign the issue to me?
Thanks!
> Add set operations to DataFrame API
> -----------------------------------
>
> Key: FLINK-40420
> URL: https://issues.apache.org/jira/browse/FLINK-40420
> Project: Flink
> Issue Type: Sub-task
> Components: API / Python
> Reporter: Liu Liu
> Priority: Major
>
> Add relational set operations to DataFrame:
> {code:java}
> def union(self, other: DataFrame) -> DataFrame
> def union_all(self, other: DataFrame) -> DataFrame
> def intersect(self, other: DataFrame) -> DataFrame
> def intersect_all(self, other: DataFrame) -> DataFrame
> def minus(self, other: DataFrame) -> DataFrame
> def minus_all(self, other: DataFrame) -> DataFrame {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
