Repository navigation
Conversation
|
Self-review of PR 19134 found no actionable implementation or test-logic issues. The delayed-batch scenario passed against the PR source in the full reactor. I removed the direct ASM dependency from Verification on JDK 17: Spotless passed; a clean source reactor build covered 37 modules and Reviewed revision: |
…r-sync-20261106 # Conflicts: # integration-test/src/test/java/org/apache/iotdb/relational/it/schema/TableMetadataPropagationTestBase.java
Description
A schema fetch registers its SchemaRegion in TableDeviceCacheAttributeGuard using put(), resetting the latest accepted update version. A delayed older batch can then overwrite current attributes, including values written after a column is dropped and re-added.
Register each region with putIfAbsent() so repeated fetches preserve its accepted version. Add a unit test for older, duplicate, and newer update versions, plus an integration test that holds an old batch across column recreation and verifies current attributes remain intact after delivery.
The integration fixture injects transport failures and delays through a Java agent in test sources. It shares cluster startup across compatible cases and exposes extra child-JVM options only in the integration-test launcher.
Validation
Initial independent review is pending; this PR is intentionally a draft.