Updates default inputSegmentSizeBytes in Compaction config

[tejaswini-imply]

Fixes Cannot serialize BigInt value as JSON error while loading compaction config in console.

Description

The reason this error is occurring is that the current default value of inputSegmentSizeBytes is Long.MAX_VALUE. Numbers over Number.MAX_SAFE_INTEGER (9,007,199,254,740,991) may not be handled by few clients like JS.

Hence reducing the default inputSegmentSizeBytes from Long.MAX_VALUE to 100,000,000,000,000 (~100TB).

---

Key changed/added classes in this PR

• DataSourceCompactionConfig

---

This PR has:

• been self-reviewed.
  • using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
• added documentation for new or modified features or behaviors.
• added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
• added or updated version, license, or notice information in licenses.yaml
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
• added integration tests.
• been tested in a test Druid cluster.

[cryptoe]

@tejaswini-imply This was very annoying. Thanks for the fix !!. Hope you have tested it locally !!

[abhishekagarwal87]

Marking it for 0.23.0 milestone as without the fix, auto-compaction dialog in console will throw an error.

[tejaswini-imply]

@tejaswini-imply This was very annoying. Thanks for the fix !!. Hope you have tested it locally !!

Yes, @cryptoe. When I tested it locally the updated default value is reflected in the console after submitting the compaction config.

[kfaraz]

LGTM

[abhishekagarwal87]

Thank you @tejaswini-imply. Can you also backport it to 0.23.0 branch?