[jdbc-v2, client-v2] Accept `1` and `0` for boolean properties

[chernser]

Description

There is a number of boolean properties in the driver and the client. Currently they may be inconsistent and accept 1 along with true. For better user experience we need it consistent and documented.

[kailash360]

@chernser I would like to work on this issue.

[kailash360]

The root cause here is inconsistent boolean parsing across jdbc-v2 and client-v2.

In some places we use Boolean.parseBoolean(...), which only treats "true" (case-insensitive) as true and everything else (including "1") as false. In other places we already have ad‑hoc handling for "1" / "0". As a result, a property set to 1 might work as expected in one code path but be silently treated as false in another.

Proposed solution

• Introduce a shared helper in the common utils module, e.g.:

  // ClickHouseUtils
  public static boolean parseBoolean(String value) {
      if (value == null) {
          return false;
      }
      if ("1".equals(value)) {
          return true;
      }
      if ("0".equals(value)) {
          return false;
      }
      return Boolean.parseBoolean(value);
  }

• Refactor:
  • jdbc-v2 (e.g. JdbcConfiguration, isSet(...), isFlagSet(...)) to use ClickHouseUtils.parseBoolean(...) for all boolean driver/client properties.
  • client-v2 (e.g. ClientConfigProperties.parseValue(...), string→boolean converters in data formats) to also use the same helper instead of Boolean.parseBoolean(...).
• Document that “Boolean properties accept true/false and 1/0” so users know what to expect.

This keeps existing true/false behavior, adds consistent 1/0 support everywhere, and centralizes the logic for easier maintenance.

[chernser]

Good day, @kailash360 !
Please go ahead.