minor: Validate batch_size configuration when setting it

[2010YOUY01]

Which issue does this PR close?

• Part of The config values aren't checked #17498

Rationale for this change

In datafusion-cli:

DataFusion CLI v53.1.0
> set datafusion.execution.batch_size=0;
0 row(s) fetched.
Elapsed 0.001 seconds.

A '0' batch_size is a invalid config value, and it's widely used in most operators to control behavior. If operators don't validate batch_size, the 0 value might cause bugs/panics. This PR rejects it when setting the config.

I triggered a bug on my first attempt:

> set datafusion.execution.batch_size=0;
0 row(s) fetched.
Elapsed 0.000 seconds.

> select * from generate_series(100);
+-------+
| value |
+-------+
+-------+
0 row(s) fetched.
Elapsed 0.004 seconds.

What changes are included in this PR?

Implement a custom type for non-zero usize configuration value on batch_size, and rejects '0' value on initialization. Rust native NonZero<u32> is not used, because custom type allows to provide better error message on errors, and the implementation complexity is similar.

Note other invalid inputs like '-1' 'a' are already rejected and covered by existing tests.

Are these changes tested?

Yes, sqllogictest

Are there any user-facing changes?

No

[comphead]

lets return config_err it would super confusing if client crashes

[2010YOUY01]

The default constructor for configurations is wrapped inside config_namespace! macro, and it can't handle ? operator on result, so we have to panic here.

But I agree this unsafe API should not be exposed to the caller, so in b37fe74, a private helper is added for unsafe construction, its input is guaranteed to be always valid, since it's only for the hard-coded default value, outside caller can only use the safe try_new()

[comphead]

maybe new with Result<Self> is more obvious choice?

[2010YOUY01]

See above comment.

[comphead]

Thanks @2010YOUY01 just some minors

[2010YOUY01]

Thank you for opening this pull request!

Reviewer note: cargo-semver-checks reported the current version number is not SemVer-compatible with the changes in this pull request (compared against the base branch).

Details

error: `cargo metadata` exited with an error:     Updating crates.io index
error: failed to get `wasm-streams` as a dependency of package `reqwest v0.12.28`
    ... which satisfies dependency `reqwest = "^0.12"` (locked to 0.12.28) of package `object_store v0.13.2`
    ... which satisfies dependency `object_store = "^0.13.2"` (locked to 0.13.2) of package `datafusion-benchmarks v54.0.0 (/home/runner/work/datafusion/datafusion/benchmarks)`

Caused by:
  failed to load source for dependency `wasm-streams`

Caused by:
  unable to update registry `crates-io`

Caused by:
  download of wa/sm/wasm-streams failed

Caused by:
  curl failed

Caused by:
  [16] Error in the HTTP2 framing layer

Looks like it's a false positive due to the flaky Github CI runner.

[Jefffrey]

what is this file?

[comphead]

🤔