Review complete at head 01eb76566c253ae33b1d76a459d9ad01c28ddea8 across all 217 changed paths. I request changes for the four inline findings: two P1 correctness/test blockers and two P2 query/reader-selection defects. There were no existing inline comments to carry forward.

Critical checkpoint conclusions:

• Goal and tests: The change makes external VARBINARY and TIMESTAMPTZ mappings consistent across connectors and adds unit and regression coverage. The new Iceberg wire test cannot exercise its intended NULL marker (P1); the Java JDBC bind tests inject dialect names directly and miss the BE parameter mismatch (P1).
• Scope: The large connector, FE, BE, and golden-result surface follows the mapping change. No unrelated change was substantiated during the file sweep.
• Concurrency: Catalog marker migration runs after fenced replay under the catalog manager write lock; journal-before-local-replay ordering was traced. No new thread-safety or lock-order defect was substantiated.
• Lifecycle: Catalog promotion/rebuild, JNI scanner and writer selection, Paimon native/JNI dispatch, and Iceberg partition write/commit lifecycles were traced. No separate ownership, cleanup, or static-initialization defect was found.
• Configuration: Catalog mapping markers are migrated and enforced as true; the legacy ORC LTZ table option is checked during scan planning. The latter check is too broad for unprojected LTZ fields (P2). No new runtime-updatable setting was identified.
• Compatibility: Production Iceberg FE uses Thrift field 20 for NULL keys, while the new manual test writes field 19 (P1). The old-FE/new-BE Iceberg FIXED-write gap is explicitly documented as an accepted rolling-upgrade limitation, so it is not reposted.
• Parallel paths: Static/dynamic Iceberg partitions, JDBC table scans/TVFs and writes, and Paimon native/JNI reads were compared. The TVF wrapper breaks a valid terminal line comment (P2); the JDBC write path sends a numeric dialect where its Java factory expects a name (P1).
• Conditions: Binary and timestamp type guards and historical-schema checks were reviewed. The Paimon full-schema LTZ condition forces JNI even without an LTZ read, and can reject a metadata-column query (P2).
• Coverage and results: BE, FE, Java, and regression tests plus 44 changed golden files were inspected. Expected types/values align with the new mappings apart from the findings above. No build or test was executed because this review's instructions require static inspection; author/CI claims were not treated as independent validation.
• Observability: The inspected error paths report failures through existing statuses/exceptions; no separate missing log or metric was substantiated.
• Persistence and failover: Catalog marker edit-log writes, replay, and master promotion were traced; no unjournaled state or distinct failover bug was established.
• Writes and atomicity: Iceberg Arrow/partition conversion and JDBC bind/transaction paths were reviewed. The JDBC handler-selection error affects TIMESTAMPTZ write semantics (P1); no separate commit or crash-safety issue was substantiated.
• FE/BE transport: The new Iceberg Thrift field is set correctly in production, while its test fixture is wrong; the JDBC enum reaches Java as the wrong string (both inline). Other changed carriers were traced without a separate issue.
• Performance and other: Unneeded Paimon JNI fallback loses native ORC splitting and parallelism (P2). No further evidenced performance or correctness issue survived the final sweep.

User focus: no additional focus was provided. All four new issues are inline; no existing blocking comment IDs apply.

Request changes. Static review of PR #68786 at f2c7b1d41ad2ba9d5ab12e2ee3b6859123ba5563 across all 219 changed files. Ten new inline findings: two P1, six P2, and two P3. The P1s are unreadable Fluss binary-partition tables after catalog migration and a MySQL mixed-timestamp predicate that can silently discard rows. The remaining findings cover Iceberg UUID partition reads, migration lock scope, PrestoDB and old Oracle zoned writes, Oracle/Trino year bounds, and two regression suites.

Convergence and prior threads. Three normal full-review passes and separate risk-focused passes covered the changed paths and their upstream/downstream carriers. Round three found three new valuable candidates; the review is incomplete under the review contract's three-round convergence limit, although every currently identified candidate has been verified and accepted or dismissed and every accepted issue is inline below. The four existing inline threads were rechecked at this head: the Iceberg Thrift NULL-key fixture and JDBC terminal-comment/Paimon fallback cases are fixed; the JDBC dialect-name P1 does not apply because the generated Thrift overload returns names and its new test covers the parameter. No existing P0/P1 comment remains applicable, so there are no carried blocker IDs. The related PR #68532 and this PR already acknowledge the mixed-version FE schema-serving window; it is recorded as a known limitation rather than a duplicate inline issue. No additional user focus was provided.

Critical checkpoint conclusions (code-review skill Part 1.3):

• Goal and proof: The change enables default VARBINARY and zoned-timestamp mappings across external catalogs and read/write transports. It adds broad unit, integration and regression cases, but the ten inline gaps mean the goal is not fully met; the tests were inspected, not run here.
• Scope and clarity: The 219-file change is broad but follows the shared mapping rollout. The two new regression blocks violate repository output/cleanup conventions; no unrelated production change was established.
• Concurrency and locks: Master promotion holds the outer CatalogMgr write lock while a deferred authorization-plugin close runs (M-002). No further new lock-order failure was substantiated. Existing connector-close work under the lock also occurs in ordinary ALTER and is a separate pre-existing pattern.
• Lifecycle and initialization: CREATE, ALTER, replay, migration, connector reset and promotion were traced. Journal-first migration and retry/checkpoint ordering are coherent; the authorization cleanup lock scope is not. No new cross-translation-unit static initializer dependency was found.
• Configuration: The binary and timestamp mapping markers are compatibility settings forced or normalized to true, rather than dynamically switchable options. That makes Fluss's unsupported binary partition mode unavoidable after migration or ALTER (M-005).
• Compatibility: FE/BE Thrift field 20 and JDBC dialect transport were rechecked; the old fixture and enum-name concerns are resolved. The acknowledged mixed-FE-version schema window remains. The newly supported zoned Oracle write path lacks an ojdbc6 bind (M-011).
• Parallel paths: Native/JNI, scalar/array, table/TVF, static/dynamic Iceberg writes, partition constants, NULL, predicates and external sinks were traced. M-001, M-004, M-007, M-008, M-010 and M-011 are the concrete mismatches; related carriers examined did not yield another distinct issue.
• Conditional checks: Paimon historical ORC field-ID routing and binary-expression guards were checked. JDBC's new instant guard misses the MySQL two-column, mixed-type comparison (M-010); the out-of-range Oracle/Trino readers lack the equivalent PostgreSQL bound check (M-007/M-008).
• Test coverage and negative cases: Added cases cover many ordinary bytes, time zones and NULLs, but omit a UUID identity scan, upgraded Fluss binary partitions, official PrestoDB and old Oracle writes, Oracle/Trino out-of-range values, and a non-UTC MySQL two-column comparison. M-003/M-009 also need runner-generated ordered output and no post-test table drop.
• Test results: Golden-output changes were inspected against the code paths; no additional wrong expected row was substantiated. No build, unit test, regression test or live database case was executed in this review, so author/CI claims are not independent validation.
• Observability: Existing catalog/connector error paths and identifiers were inspected; no separate missing log or metric was substantiated. Explicit range rejection would make M-007/M-008 diagnosable instead of packing unsupported years.
• Persistence and transactions: Catalog marker logs are written before local apply, replay reproduces the marker, and crash/retry/checkpoint ordering appears coherent. No new storage visible-version, delete-bitmap or transaction-log inconsistency was found.
• Writes and crashes: Iceberg static/dynamic partition routing, typed commit values and file cleanup were traced without another proven atomicity or crash leak. The concrete new write failures are M-004 and M-011; the lock issue is M-002.
• FE-to-BE values: The new Thrift NULL-key field and JDBC dialect/parameter transport were checked at each sender/reader reached by the diff; no additional missing propagation was found.
• Performance: Paimon schema checks are cached by scan context/schema ID, and no distinct unbounded allocation or hot-loop regression was proven. Slow plugin cleanup under the global catalog lock is the concrete contention issue (M-002).
• Other issues: The remaining speculative or already-reported candidates were dismissed with code evidence or existing review context. The ten comments below are the complete accepted set from this capped static review.

Review complete at head 542257b6961afcc5d7c93c4bd170dc82f0320a05 after two convergence rounds and a final sweep of all 239 changed paths. Request changes: the new MySQL timestamp predicate case can silently discard rows. The three inline comments cover that case, Iceberg binary partition metadata, and regression test standards. No additional user review focus was supplied. This was static inspection; no build or test was run.

Code-review checkpoints:

1. Goal and tests: The change wires binary and zoned timestamp mappings through FE, JNI, BE, catalog migration, and Iceberg writes, with new unit and regression source. The reported JDBC and Iceberg paths prevent complete correctness, and their specific cases lack coverage.
2. Scope and clarity: The broad change follows the required cross-layer type contracts. No unrelated production change was substantiated as a separate issue.
3. Concurrency and locks: Master promotion journals and applies marker updates under the catalog write lock. Authorization cleanup is deferred until unlock, while connector close can still perform I/O under that lock; this residual is within existing P2 thread 4218883248. No new lock-order or deadlock path was established.
4. Lifecycle: Promotion gates serving, replays the journal, migrates markers, then resumes checkpoint/service work. Reset and connector rebuild paths were traced; no distinct retry or startup divergence was found.
5. Configuration: CREATE, ALTER, and migration normalize the two mapping markers to true. This is an intentional one-way compatibility migration; no dynamic toggle is promised.
6. Compatibility: The static-null Thrift set uses field 20 and FE/BE agree on its representation. Supported rolling upgrades put BE before FE; acknowledged mixed-version limitations remain. No external file rewrite is introduced.
7. Parallel paths and conditions: Legacy and plugin JDBC, CDC/TVF exceptions, external connector reads, and Iceberg static/dynamic writes were compared. The JDBC guard handles wall-clock columns but misses literals; Iceberg's partition-key builder still lacks VARBINARY.
8. Coverage and results: Relevant tests and generated output changes were inspected, never executed here. New regression checks listed in the P3 comment lack generated output; the reported JDBC literal and Iceberg identity-partition cases are not covered.
9. Observability and errors: FE warns when partition-item creation fails but then reports the table unpartitioned, obscuring the loss of pruning. Other error/status and BE null/constant handling examined did not yield a distinct new finding.
10. Persistence and failover: Catalog ALTER logging precedes application, and follower replay/retry use the persisted markers. No new EditLog or checkpoint inconsistency was established.
11. Writes and crash paths: Iceberg NULL, binary, UUID, timestamp, full-static, hybrid, overwrite, transform, and commit transports were traced. No separate atomicity or crash-leak defect was substantiated.
12. FE/BE transport: New binary/instant carriers and the Thrift NULL marker were checked on both sides; the older UUID scan-transport thread is addressed.
13. Performance, memory, and other paths: The Iceberg finding disables FE partition pruning. Fluss still loses FE binary partition metadata/pruning, but its earlier P1 listing/SELECT outage is fixed and the narrower residual belongs to existing thread 4218883211. No distinct memory-accounting or further performance issue survived recheck.

Existing P1 threads 4217826031, 4217826038, 4218883211, and 4218883225 were independently checked; none remains applicable at its reported P1 failure mode, so no existing blocker ID is carried.

Review status: INCOMPLETE under the requested three-round convergence rule: the final risk pass found a new, independently validated Hive ORC V1 issue (M-9), so another no-new-findings round could not be run. All 265 changed paths were covered in each normal pass, every raised candidate has a disposition, and all eight accepted findings are inline below. Two are P1 (Iceberg partition/file identity and official PrestoDB zoned-array scans); six are P2 (four external JNI timestamp range paths, nested MaxCompute writes, and Hive ORC V1 range packing). I recommend changes before merge.

Existing P1 disposition: no previously reported P1 still applies with its original scope at this head, so existing_blocking_comment_ids is empty. The BE Thrift test uses field 20; the JDBC dialect name resolves the generated Thrift to_string overload; upgraded Fluss nodes decode binary partition names (the conditional old-follower failover case is deduplicated against that thread at lower severity); and both JDBC mixed-timezone predicate forms are held local by hasWallClockValue with remote LIMIT suppressed when a filter is dropped. Existing P2/P3 inline threads remain duplicate fences and were not reposted. The user focus file listed no additional focus.

Code-review critical checkpoints:

1. Goal and tests: the change aims to preserve external binary bytes and zoned instants across read/write paths. Ordinary, NULL, DST, pre-epoch, partition, and nested fixtures were added, but the eight findings show the goal is incomplete and their boundary/mixed-value cases lack coverage.
2. Scope: the 265-path change is broad but centered on type mapping, transport, catalog migration, and tests; no unrelated production edit was identified.
3. Concurrency: catalog migration journals/applies under the global catalog write lock and performs detached cleanup after unlock; writer caches are per sink instance. The Iceberg path-key collision is a correctness fault, not a lock race; no separate lock-order or shared-state defect survived.
4. Lifecycle/statics: connector reset/close and master-promotion sequencing were traced; function-local epoch statics have ordered initialization. No new cross-translation-unit initializer dependency or unreleased lifecycle was found.
5. Configuration: legacy binary/instant mapping flags now normalize to true on CREATE/ALTER and replay; no new process setting requiring dynamic propagation was added. The existing force_jni_scanner and enable_file_scanner_v2 switches were checked for reachable paths.
6. Compatibility: optional Thrift field 20 agrees across FE, BE, and the fixed fixture. The old-follower Fluss case is already in an existing thread; no other new rolling-format issue was substantiated.
7. Parallel paths: legacy/plugin JDBC, native/JNI, Parquet/ORC, scalar/nested, TVF/table, and read/write counterparts were compared. Source-specific gaps are recorded separately in the inline findings.
8. Conditions: JDBC wall-clock predicate guards and dropped-filter LIMIT handling, Paimon historical field-ID fallback, and static/hybrid NULL branches were traced; no additional incorrect guard survived.
9. Test coverage: changed unit/integration and regression suites exercise common and selected negative cases, but miss the accepted official-driver, year-10000, mixed Iceberg binary/NULL, and nested MaxCompute cases.
10. Expected results: changed .out fixtures were compared with ordered queries by static inspection; their execution and generation were not independently verified. Existing style comments cover fixed assertions and post-run drops.
11. Observability: ordinary connector/BE errors retain identifying context, while the silent invalid timestamp packing and mislabeled Iceberg file are the issues reported here; no distinct metrics/logging gap was proven.
12. Persistence/failover: marker migration journals before local apply and replay restores it after a crash; the residual mixed-version Fluss concern was deduplicated with the prior thread.
13. Writes/atomicity: Iceberg can commit a file with rows from two logical partitions under one first-row partition value; nested MaxCompute zoned writes fail before completion. Other inspected write and cleanup paths showed no separate atomicity defect.
14. FE/BE variables: the mapping markers and optional NULL-key Thrift field are passed to the relevant readers/writers; typed partition value and JNI timestamp transport were traced end to end.
15. Performance/memory: projected/historical Paimon checks and connector conversions were inspected for repeated work and allocation; no distinct material regression was substantiated.
16. Other issues: the final changed-file/accepted-anchor sweep found no unresolved candidate, while the final-round new issue leaves convergence incomplete as stated above.

Validation was static only as required: no build, test, or source edit was performed. The read-only BE header-hygiene gates passed; inspected test files and author/CI claims are not independent execution evidence.

Follow-up FE review of 73dd4b8:

Preserving native UUID is the right direction. The previous UUID-typed input, recursive MAP conversion, MySQL double-minus, and NO_BACKSLASH_ESCAPES findings are addressed in this revision.

Please also revisit these three existing P2 threads; their triggering paths remain at this head:

• Evaluate a volatile STRUCT input once: inline VALUES can still reconstruct fields from different evaluations and store a mixed record.
• Use canonical UUID text in LIST partition metadata: the remaining 0x carrier fails UUID parsing and drops non-null UUID partitions from the FE partition view/counts; file scanning itself still enumerates the files.
• Select the Paimon legacy ORC reader from the historical file schema: an added LTZ column can force an old file with no LTZ bytes into JNI and reject an otherwise valid physical-metadata query.

I added one new inline comment on Trino JDBC UUID predicate literals. These concrete issues should be addressed before merging. This review is based on source and dependency inspection; no local build or runtime tests were run.

Static review complete for head 30130849adb2423c897241f73b9745b521e4cc56 after two review rounds and a final sweep of all 350 changed paths. I found one new P2 issue, reported inline. Existing P1 comment 4217826038 still applies: the BE JDBC writer sends a numeric dialect to a JNI factory that selects handlers by name, skipping dialect-specific TIMESTAMPTZ write handling. I carried that comment ID without reposting it. The other examined P1 comments are fixed on this head. There was no additional user review focus.

Critical checkpoints:

• Goal and scope: The PR moves external binary, UUID, and timestamp mappings through FE, BE, and JNI. The related adapters and regression coverage are broad but tied to that goal. The V1 ORC year-zero boundary remains incorrect.
• Concurrency: Catalog migration runs under the catalog write lock; journal writes precede application and deferred cleanup runs after unlocking. No separate lock-order or race issue was substantiated.
• Lifecycle: Master promotion, replay, catalog cache reset, and connector ownership were traced. No new lifecycle or static-initialization defect was substantiated.
• Configuration: CREATE, ALTER, and promotion normalize the existing mapping markers to the new effective policy. No new dynamic setting was introduced; the existing scanner setting exposes the V1 ORC issue.
• Compatibility: Mixed FE/BE UUID, Hudi timestamp, MaxCompute timestamp, and legacy FIXED paths are covered by existing inline threads. The existing JDBC writer P1 remains applicable; the old V1 UUID equality-delete P1 is fixed.
• Parallel paths and conditions: V1/V2 file readers, native/JNI fallback, and partition read/write paths were traced. The new V1 lower-bound condition rejects a value V2 and Doris accept. Other investigated conditions were either fixed or already threaded.
• Test coverage: New unit tests, regression suites, and expected outputs were inspected statically. The year-zero ORC fixture exercises V2 only; V1 boundary coverage is missing. No builds or tests were run, as required by this review invocation, so runtime results are unverified.
• Test results: Changed suite labels and recorded outputs were checked for consistency; no distinct output mismatch was substantiated. The newly added JDBC writer test statically expects dialect names that the current BE path does not send.
• Observability and errors: The changed readers and writers propagate errors with context; no independent logging or metrics gap was substantiated.
• Persistence: The catalog marker migration journals before applying changes and reuses ALTER replay; promotion, failure, and idempotence test paths were inspected without a separate persistence finding.
• Writes and crashes: Iceberg static and dynamic partition encoding, NULL/binary writer keys, and sink coercion were traced. The JDBC dialect mismatch above remains the write-side blocker; no other unthreaded atomicity or crash issue was substantiated.
• FE/BE contract: No Thrift or protobuf definitions changed. Existing carriers and rolling-upgrade paths were reviewed; previously reported compatibility concerns were not duplicated.
• Performance and other paths: Query-TVF planning overhead is already covered by existing threads. No further distinct performance or correctness issue survived validation and deduplication.

Existing P0/P1 findings confirmed for this head: #68786 (comment)

Static review of PR #68786 at head 3013084 (350 changed paths). Four new inline findings: one P1 and three P2. All 78 existing inline comments were checked for duplicates. Ten earlier P1 comments were independently rechecked and no longer apply at this head; there are no carried P0/P1 blocking IDs. The user supplied no additional review focus.

Review completion: All current candidate findings have been resolved and the final changed-file sweep found no uncovered path. Convergence remains incomplete: new distinct findings appeared in round 3, and the required three-round cap prevents a further convergence pass. This is a static review; no build, test, or runtime validation was performed.

Critical checkpoints

• Goal and proof: The PR aims to preserve native binary, UUID, and timestamp semantics across external connectors and writes. The four inline failures show that the Iceberg BINARY path does not yet meet that goal. The added tests inspected do not prove these V1 delete, set operation, window, or nested-key cases.
• Scope and clarity: The migration spans 350 paths across BE, FE, connector Java, and regression suites. The changed type mapping is clear, but its effects on unchanged hash consumers are not fully covered.
• Concurrency: Catalog promotion, replay, scan routing, and writer-key paths were traced. No additional lock-order or shared-state race was substantiated in the inspected paths.
• Lifecycle: Migration journals markers before master readiness; scan and writer close paths were checked. No separate lifecycle or cross-translation-unit static-initialization failure was established.
• Configuration dynamics: Legacy mapping flags are normalized during promotion and ALTER; current code makes the new logical mapping effective without relying on a dynamic flag refresh. No distinct unreported configuration issue was established.
• Compatibility: Rolling-version, stored catalog, view, and FE/BE type contracts were checked against existing threads. Previously raised P1s are fixed on this head; the new Iceberg BINARY failures are separate compatibility regressions.
• Generated wire definitions: No gensrc/thrift or gensrc/proto file changed, so field-ID and enum compatibility checks do not apply.
• Parallel paths: V1/V2 file readers, Iceberg delete paths, JDBC scanner/writer routes, Paimon native/JNI routes, and BE set/hash dispatch were compared. The four inline issues are the distinct missing paths found.
• Conditional checks: FE guards reject scalar VARBINARY grouping and joins, but omit set operations and window partitioning and do not recurse into array element types. The related BE hooks still throw; see inline findings.
• Coverage: Existing regression and unit changes were inspected, including expected-output files. Targeted positive and negative coverage is missing for the four reported execution paths.
• Test results: Expected-output changes were reviewed statically only. Their runtime correctness cannot be certified because the review instructions prohibited builds and tests.
• Observability: The failing BE paths return explicit unsupported-operation errors. No additional logging or metric defect was substantiated.
• Persistence: Catalog migration journal ordering, replay, and master promotion were traced; no separate unjournaled-state defect was established.
• Writes and atomicity: Typed Iceberg writer keys, nullness separation, static partition metadata, and commit paths were checked. Previously reported write issues are fixed or already covered by existing comments; no new atomicity defect was established.
• FE/BE variables: Mapping options, schema context, UUID/binary types, timestamp handling, and partition nullness were followed across FE/BE carriers. No separate missing carrier was established.
• Performance: Scan selection, JNI projection, partition routing, and hashing paths were examined. No distinct CPU, memory, or asymptotic regression was substantiated beyond the functional failures above.
• Other issues: Remaining candidate points were either duplicates of existing inline comments or dismissed with concrete downstream evidence. No unresolved candidate remains within the completed three rounds.

Review conclusion

Static review of PR #68786 at head 30130849adb2423c897241f73b9745b521e4cc56. The patch moves external binary, UUID, and instant values to their native types across FE schemas, native BE readers/writers, and JNI connectors. I found the inline issues below in current reads and in both rolling-upgrade directions. The active V1 BINARY equality-delete P1 is already reported in comment 4237058215; I confirmed it still applies and carried its ID without reposting it. Older UUID equality-delete and year-zero scanner-test P1 comments are fixed at this head. There was no additional user review focus.

Convergence status: incomplete. The capped third full-review round found the converted-only Parquet timestamp issue. All known candidates from the three rounds were checked and resolved into an inline finding, an existing thread, or a concrete dismissal, but the required no-new-finding convergence was not reached before the three-round limit.

Critical checkpoints

• Goal and proof: Native types preserve intended binary bytes, UUID semantics, and timestamp instants on several new paths, but the reported file-reader, JDBC, native connector, and mixed-version failures prevent the change from meeting that goal for all supported data. New unit and regression cases cover many current-version types; they do not prove the mixed-version and historical-file cases reported here.
• Scope and focus: Reviewed the authoritative 350 changed paths across BE, FE connectors/core/SPI, Java extensions, and regression output. The cross-module scope follows the type-contract change; no separate user focus was supplied.
• Concurrency and locking: Catalog marker migration journals and applies under the catalog global write lock, with deferred cache cleanup after release. No new lock-order, race, or heavy work inside a lock was substantiated beyond already threaded old-follower behavior.
• Lifecycle: Checked master promotion/replay, catalog cache reset, Paimon fallback split and iterator ownership, JDBC connection initialization, and BE writer open/close. The Oracle-mode OceanBase initialization and old-BE ORC writer assertion are the actionable lifecycle failures; no separate ownership or static-initialization defect was found.
• Configuration: Legacy mapping flags become effectively enabled and are migrated through the catalog path. This exposes native FE slots while old BEs still serve scans/writes; no BE capability gate is present for the reported paths. Existing threads cover old-follower, stored-view, and MTMV consequences of the metadata migration.
• Compatibility: Both upgrade directions and historical file annotations were traced. Existing threads cover several old-FE/new-BE cases; the new inline findings cover distinct FE-first/old-BE consumers and current-BE Hudi/Parquet representation gaps. No gensrc/thrift or gensrc/proto file changed, so there is no new field-ID contract to audit.
• Parallel paths: Checked V1/V2 Parquet and ORC, Hudi COW/MOR, native Trino and JDBC scans, MaxCompute read/write, Iceberg partitioned and unpartitioned sinks, and Paimon/Fluss/Hive paths. The reported issues are distinct in their consumer or physical carrier; remaining plausible parallel cases were covered by existing threads or had matching dispatch.
• Conditions and error handling: The old ORC UUID path treats a newly valid FE type as an invariant violation and can abort a BE. Other unsupported conversions/handler cases surface errors rather than being silently ignored; the timestamp read/bind cases can silently shift instants. No further ignored Status or catch boundary issue was substantiated.
• Tests and results: Inspected changed unit/regression cases and .out entries statically, including negative and ordered-result cases. Mixed-version scans/inserts, Hudi COW Parquet UUID, and converted-only Parquet timestamp files need coverage. The review prompt prohibits builds and tests, so no runtime pass claim is made.
• Observability: Existing conversion and JNI errors expose the failure stage; no independent missing log or metric issue was substantiated. Silent timestamp shifts need the proposed non-UTC tests.
• Transactions and persistence: Catalog migration journals before apply and follows replay on promotion. Existing threads report remaining old-follower and persisted-object consistency effects. No additional journal/replay mismatch was established.
• Writes and atomicity: Iceberg and MaxCompute mixed-version writes can fail before file/commit completion; PostgreSQL JDBC can persist the wrong instant on an old BE with a non-UTC JVM. No additional transaction atomicity, leak, or commit-metadata defect was substantiated on current BEs.
• FE–BE transport: Existing slot and JNI columns_types transport conveys the new types, but the old per-connector handlers and writers lack matching support. No new wire variable or field was added; capability/version handling is the missing contract.
• Memory, nullability, and data correctness: Reviewed BE nullable/const handling, UUID SerDe and Arrow ownership, partition NULL keys, binary hash/JSON consumers, and type conversion. No independent allocator, lifetime, or nullable-shape issue survived review. The existing V1 BINARY equality-delete P1 and the new type/instant issues are the data-correctness blockers.
• Performance and other risks: The JDBC SQL-mode round-trip concern is already in an existing thread. No further distinct CPU, memory, or scalability regression was substantiated in this static pass.

Existing P0/P1 findings confirmed for this head: #68786 (comment)