[Bug]: Some TableProperties should not be modified and may cause data consistency issues
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 395
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 33
Description
### Search before asking
- [X] I have searched in the [issues](https://github.com/NetEase/arctic/issues?q=is%3Aissue) and found no similar issues.
### What would you like to be improved?
Certain properties should not be allowed to be modified via the interface such as 'table.partition-properties', and 'base.table.max-transaction-id' etc.
Modification of these properties may result in metadata corruption or data consistency issues.
### How should we improve?
Restrictions on the modification of certain properties at code level
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Subtasks
_No response_
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating the interface that modifies table properties and the definitions of table.partition-properties and base.table.max-transaction-id. Done means restricted properties cannot be modified through that interface, with coverage for the metadata consistency risk.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100