QuakeWang opened a new pull request, #263:
URL: https://github.com/apache/paimon-rust/pull/263
<!--
Thank you very much for contributing to Paimon Rust - we are happy that you
want to help us improve it. 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
- Make sure that the pull request corresponds to a [GitHub
issue](https://github.com/apache/paimon-rust/issues). Exceptions are made for
typos in documentation or comments, which need no issue.
- Fill out the template below to describe the changes contributed by the
pull request. That will give reviewers the context they need to do the review.
- Make sure that the change passes the automated tests, i.e., `cargo test`
passes.
- Each pull request should address only one issue, not mix up code from
multiple issues.
**(The sections below can be removed for hotfixes or typos)**
-->
### Purpose
<!-- Linking this pull request to the issue -->
part of: #256
This PR just for `partial-update` merge engine without claiming end-to-end
support yet, and focuses on parsing, validation, merge-core preparation, and
fail-fast safety rails so Rust Paimon does not silently read or write
`partial-update` tables with incorrect semantics.
<!-- What is the purpose of the change -->
### Brief change log
<!-- Please describe the changes made in this pull request and explain how
they address the issue -->
- add `MergeEngine::PartialUpdate` parsing support
- introduce `PartialUpdateConfig` to centralize partial-update option
validation
- reject unsupported advanced partial-update options such as
sequence-group, aggregate-function, and partial-delete related options
- add fail-fast checks for PK partial-update reads and writes
- disable limit pushdown hints for PK partial-update tables
- generalize the sort-merge contract so merge functions can return
materialized rows, preparing the merge core for future field-wise
partial-update implementation
- add regression tests to keep existing `first-row` and current merge
behavior stable
### Tests
<!-- List unit tests or integration cases to verify this change -->
### API and Format
<!-- Does this change affect API or storage format -->
### Documentation
<!-- Does this change introduce a new feature or require documentation
updates -->
--
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]
