Skip to content

docs: correct three wrong default values in CoreOptions doc comments - #640

Open
jackylee-ch wants to merge 1 commit into
apache:mainfrom
jackylee-ch:docs/fix-core-options-doc-defaults
Open

docs: correct three wrong default values in CoreOptions doc comments#640
jackylee-ch wants to merge 1 commit into
apache:mainfrom
jackylee-ch:docs/fix-core-options-doc-defaults

Conversation

@jackylee-ch

Copy link
Copy Markdown
Contributor

Three accessor doc comments in core_options.rs state defaults that disagree with
the constants right next to them:

  • bucket() says "Default is 1" but DEFAULT_BUCKET is -1. The existing test
    asserts bucket() == -1, and Java defaults to -1 too — the comment is the
    only thing wrong.
  • target_file_size() says "Default is 128MB" but DEFAULT_TARGET_FILE_SIZE is
    256 MiB. Java gives this option no default and documents 128 MB for primary-key
    tables / 256 MB for append tables, so the comment now records which one this
    returns.
  • dynamic_bucket_target_row_num() claims 200,000 "matching Java Paimon", but
    Java defaults dynamic-bucket.target-row-num to 2,000,000. This states the
    difference rather than asserting parity; the constant is left unchanged
    happy to follow up if you want the value aligned instead.

Comments only, no behavior change.

Three accessor doc comments state defaults that disagree with the constants
right next to them:

- `bucket()` says "Default is 1" but `DEFAULT_BUCKET` is `-1`; the existing test
  asserts `bucket() == -1`, and Java defaults to `-1` as well.
- `target_file_size()` says "Default is 128MB" but `DEFAULT_TARGET_FILE_SIZE` is
  256 MiB. Java gives `target-file-size` no default and documents 128 MB for
  primary-key tables and 256 MB for append tables, so record which value this
  returns.
- `dynamic_bucket_target_row_num()` claims 200,000 matches Java, but Java
  defaults `dynamic-bucket.target-row-num` to 2,000,000. State the difference
  instead of asserting parity; the constant is left alone.

Comments only, no behavior change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant