lilei1128 opened a new pull request, #3361:
URL: https://github.com/apache/fluss/pull/3361
<!--
*Thank you very much for contributing to Fluss - we are happy that you want
to help us improve Fluss. To help the community review your contribution in the
best possible way, please go through the checklist below, which will get the
contribution into a shape in which it can be best reviewed.*
## Contribution Checklist
- Make sure that the pull request corresponds to a [GitHub
issue](https://github.com/apache/fluss/issues). Exceptions are made for typos
in JavaDoc or documentation files, which need no issue.
- Name the pull request in the format "[component] Title of the pull
request", where *[component]* should be replaced by the name of the component
being changed. Typically, this corresponds to the component label assigned to
the issue (e.g., [kv], [log], [client], [flink]). Skip *[component]* if you are
unsure about which is the best component.
- Fill out the template below to describe the changes contributed by the
pull request. That will give reviewers the context they need to do the review.
- Make sure that the change passes the automated tests, i.e., `mvn clean
verify` passes.
- Each pull request should address only one issue, not mix up code from
multiple issues.
- **Generative AI disclosure:** Indicate whether generative AI tools were
used in authoring this PR. If yes, specify the tool below.
- [ ] No generative AI tools used
- [ ] Yes (please specify the tool below)
**(The sections below can be removed for hotfixes or typos)**
-->
<!--
Generated-by: [Tool Name and Version] following [the
guidelines](https://github.com/apache/fluss/blob/main/AGENTS.md)
-->
### Purpose
<!-- Linking this pull request to the issue -->
Linked issue: close #3315
<!-- What is the purpose of the change -->
Add five new table-scoped ConfigOptions (table.log.segment.file-size,
table.log.index.file-size, table.log.index.interval-size,
table.log.file-preallocate, table.log.flush.interval-messages) that
override the corresponding cluster-level log.* settings for a single
table when explicitly set. Tables without these properties continue
to use the server-global values unchanged.
### Brief change log
<!-- Please describe the changes made in this pull request and explain how
they address the issue -->
- ConfigOptions: add TABLE_LOG_* options with noDefaultValue() so
absent values fall back to server config automatically
- FlussConfigUtils: register all five keys in ALTERABLE_TABLE_OPTIONS
so ALTER TABLE SET takes effect on the next segment roll
- TableDescriptorValidation: add overflow guard for
table.log.segment.file-size (mirrors existing server-level check)
- LogTablet: add buildEffectiveLogConfig() helper and a new create()
overload that accepts tableProperties; old overload delegates with
an empty Configuration for full backward compatibility
- LogManager: thread tableProperties through getOrCreateLog() and
loadLog() so both the online and recovery paths honour overrides
- Replica: pass tableInfo.getProperties() into getOrCreateLog()
### Tests
<!-- List UT and IT cases to verify this change -->
- LogTabletTest: verify segment roll and auto-flush behaviour with
table-level overrides vs. server defaults
- TableDescriptorValidationTest: cover valid values, Integer.MAX_VALUE
boundary, overflow rejection, and TABLE_OPTIONS registration for
all five new keys
### API and Format
<!-- Does this change affect API or storage format -->
### Documentation
<!-- Does this change introduce a new feature -->
--
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]
