damokelis commented on PR #66790: URL: https://github.com/apache/doris/pull/66790#issuecomment-5329000222
Pushed 4 new commits extending this PR from read/insert support to the full write surface for Paimon 2.0: - `[fix](build)` hive-shade artifact via explicit outputFile (clean builds failed with *main artifact does not exist*) - `[fix](filesystem)` accept the dotted `s3.path.style.access` alias every existing regression catalog uses (silently defaulting to false breaks hostname-addressed S3-compatible endpoints; CI never saw it because an IP endpoint force-switches the SDK to path style) - `[feature](paimon)` column schema evolution — ALTER TABLE ADD/DROP/RENAME/MODIFY COLUMN, flat and nested dotted-path, with nullability/comment change gates and a statement-fence pin that no longer time-travels the schema generation - `[feature](paimon)` row-level DELETE / UPDATE / MERGE INTO — keyed writes on primary-key tables (operation-tagged stream), deletion-vector DELETE on unaware-bucket append tables (merging with existing vectors), actionable rejections elsewhere Capability matrix as implemented and verified end-to-end (minio + FE + BE from this branch, both new regression suites green): | table shape | ALTER | DELETE | UPDATE | MERGE | |---|---|---|---|---| | primary-key | ✅ flat+nested | ✅ keyed | ✅ | ✅ incl. matched-delete | | append-only + deletion vectors (unaware bucket) | ✅ | ✅ DV write + vector merge | rejected with hint | rejected | | append-only w/o vectors, bucketed append | ✅ | rejected with hint | rejected | rejected | Two pre-existing issues surfaced while validating and are worth separate attention: (1) several assembly descriptors reference reactor modules their pom does not declare (e.g. fe-core's make-fe-lib packaging hadoop-deps), so a clean `mvn package` hits *isn't a file* unless retried — build.sh's retry masks it; (2) `ColumnPath.fromDotName` has no callers — nested column DDL only enters through the parser's multipart identifier path. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
