[Feature] Generating changelogs with Python writers for input changelog-producer
- Dominant language
- Java
- Stars
- 3.4k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 396
Description
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar.
### Motivation
Currently the Python write path never produces changelog files. CommitMessage has no changelog field, DataWriter writes only one file, and FileStoreCommit creates snapshots with changelog_manifest_list=None.
### Solution
Implement INPUT mode only (double-write at flush time). FULL_COMPACTION and LOOKUP require compaction infrastructure that doesn't exist in Python at the moment.
### Anything else?
_No response_
### Are you willing to submit a PR?
- [x] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing CommitMessage, DataWriter, and FileStoreCommit to understand the current Python write and snapshot paths. Done means INPUT mode double-writes changelog files at flush time and snapshots populate the changelog manifest; FULL_COMPACTION and LOOKUP remain out of scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100