[FLINK-37125] [conf] fixed env.log.max java.lang.NumberFormatException

[sehajsandhu123]

What is the purpose of the change

Fix for NumberFormatException in Log Configuration
This PR resolves an issue where the log.max parameter in config.yaml was treated as a string, causing a java.lang.NumberFormatException when parsed by the DefaultRolloverStrategy plugin.

Changes:
Updated the config.sh script to clean up MAX_LOG_FILE_NUMBER by removing leading and trailing single quotes before parsing.

Testing:
Verified correct parsing of config env.log.max in a real Hadoop 3.3.6 cluster.
Confirmed the history server starts without errors after the change.

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (no)
• The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
• The serializers: (no)
• The runtime per-record code paths (performance sensitive): (no)
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
• The S3 file system connector: (no)

Documentation

• Does this pull request introduce a new feature? (no)
• If yes, how is the feature documented? (not applicable)

[flinkbot]

CI report:

• 1a099c6 Azure: FAILURE

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[davidradl]

This fix is tolerating a string for a field that should be numeric. Would it not be better to check that the token is a number and give an error if it is not a number (e.g. if it is a string including a string that is a quoted number?)

[davidradl]

Reviewed by Chi on 23/01/2025 Go back to the submitter with review comments.

[sehajsandhu123]

@davidradl
The reason for tolerating strings is that ConfigurationParserUtils.loadAndModifyConfiguration inherently processes all YAML configuration values as strings due to how Configuration.toFileWritableMap serializes data using YamlParserUtils.toYAMLString. This results in numeric values being wrapped as strings (e.g., '10').

This fix handles this behaviour by removing unnecessary quotes to ensure the value is interpreted correctly. Adding an error check here might result in false positives, as numeric values are always converted to strings in config.yaml