[FLINK-40435][python] Add explode support to DataFrame API - #29196
Open
beetle0915 wants to merge 1 commit into
Open
beetle0915 wants to merge 1 commit into
beetle0915 wants to merge 1 commit into
Conversation
Generated-by: OpenAI Codex CLI 0.154.0-alpha.6.2
Collaborator
beetle0915
marked this pull request as ready for review
September 15, 2026 16:17
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the purpose of the change
Add
DataFrame.explode()as specified in FLIP-591 and FLINK-40435, exposing collection expansion through the DataFrame API.Brief change log
ignore_empty_and_null=True.Verifying this change
Local validation uses Python 3.12.11, Java 17.0.14 and Maven 3.9.16. Both Python source and Java artifacts come from this PR's commit
447edf29025, based on master atbd0a65afb94. The distribution and Python test dependencies were freshly built in an isolated Maven repository. Loaded Table API/runtime JAR paths and the extracted Planner hash were checked against the new build../mvnw -B -T2 -pl flink-dist,flink-python -am -DskipTests -Pskip-webui-build installwith the isolated local repository: BUILD SUCCESS, 106 modules (16m57s). This builds artifacts and test classes; it does not execute the Java tests or build the Web UI.python -m pytest -q --tb=short pyflink/dataframe/testsagainst the new distribution: 371 passed, 8 existing deprecation warnings (109.37s)../mvnw -B -pl flink-table/flink-table-planner -Dtest=UnnestTest,LogicalUnnestRuleTest,UnnestITCase testwith the same local repository: 175 passed, no failures, errors or skips; covers logical rules, batch/stream plans and batch/stream execution.python -m flake8 --config=tox.ini pyflink/dataframe: passed.python -m mypy --config-file tox.ini: passed for 83 source files.-W --keep-going: passed.git diff origin/master --check: passed.Full-repository Maven verification and community CI validation remain outstanding; this PR remains a draft.
The existing UNNEST behavior that drops null ROW elements is tracked separately in FLINK-40658. It reproduces through direct Table API/SQL without this change. This PR does not fix that behavior; the separate reproduction is in that ticket.
Does this pull request potentially affect one of the following parts:
@PublicEvolvingDataFrame method specified by FLIP-591.Documentation
Was generative AI tooling used to co-author this PR?
Generated-by: OpenAI Codex CLI 0.154.0-alpha.6.2