csurong opened a new pull request, #29245:
URL: https://github.com/apache/flink/pull/29245

   ## What is the purpose of the change
   
   Add Parquet and JSON filesystem I/O to the PyFlink DataFrame API, as 
described in [FLINK-40426](https://issues.apache.org/jira/browse/FLINK-40426) 
and FLIP-591.
   
   ## Brief change log
   
   - Add `read_parquet`, `read_json`, `write_parquet`, and `write_json`, using 
the existing filesystem connector.
   - Support format options and append/overwrite writes while preserving 
`write_generic` behavior.
   - Add tests and API documentation with a usage example.
   
   ## Verifying this change
   
   - [Flink CI (Java 
17)](https://github.com/csurong/flink/actions/runs/35483836376) passed, 
including basic QA, compilation, packaging/licensing, tests, and end-to-end 
tests.
   - All 21 tests in `test_filesystem_io.py` and `test_io.py` passed, including 
real JSON/Parquet reads and writes, write modes, format options, and argument 
validation.
   - Flake8, targeted mypy checks, strict Sphinx build, and a clean build of 
`flink-python` with its dependencies passed (Java tests skipped in that build).
   - Full `clean verify` was attempted, but four OpenTelemetry tests failed 
because no Docker environment was available locally.
   
   ## Does this pull request potentially affect one of the following parts:
   
   - Dependencies: no
   - Public API: yes, the Python helpers specified in FLIP-591
   - Serializers: no
   - Runtime per-record code paths: no
   - Deployment or recovery: no
   - S3 file system connector: no
   
   ## Documentation
   
   - New feature: yes
   - Documented in the Python API docstrings and DataFrame I/O reference.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (please specify the tool below)
   
   Generated-by: OpenAI Codex (GPT-6)
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to