Hastyshell opened a new pull request, #63173:
URL: https://github.com/apache/doris/pull/63173
### What problem does this PR solve?
Issue Number: None
Related PR: None
Problem Summary: Re-adding a dropped value column with the same name can
reuse the dropped column's unique id when legacy metadata has a stale
`maxColUniqueId`, causing old segment data to be read as the new column.
### Release note
Fix re-added same-name columns reading stale data after light schema change
with stale column unique id metadata.
### Check List (For Author)
- Test: Unit Test
- Added `SchemaChangeHandlerTest` coverage for re-adding a dropped value
column with stale `maxColUniqueId`.
- Ran: `cd fe && mvn checkstyle:check -pl fe-core -am
-DfailIfNoTests=false`.
- Tried: `./run-fe-ut.sh --run
org.apache.doris.alter.SchemaChangeHandlerTest#testReaddDroppedValueColumnUsesNewUniqueId`;
FE test fork failed before running tests because surefire could not open
literal `@{argLine}`.
- Behavior changed: Yes. New columns no longer reuse historical dropped
column unique ids when `maxColUniqueId` metadata is stale.
- Does this need documentation: No
--
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]
