[coverage] Conformance findings: LOGGING-002

[peco-engineer-bot]

Summary

Surfaced by the multi-language coverage fan-out while conformance-testing these SPEC-IDs against databricks/databricks-jdbc. Each finding is committed as an expected-failure (xfail) test in the coverage PR — the test asserts the CORRECT (post-fix) behavior and stays red until THIS driver (databricks/databricks-jdbc) is fixed, then flips green as a tripwire.

Findings

• LOGGING-002 [thrift, sea]: LogPath is always resolved as a directory (JulLogger.getLogPattern does Files.createDirectories then resolves databricks_jdbc.log inside), so a caller-supplied log FILE path is silently created as a directory instead of being written verbatim
  • failing test: testDirectoryLogDestinationResolvesToALogFileInsideIt (see the coverage PR diff under tests/)
• LOGGING-002: LogPath is always resolved as a directory (JulLogger.getLogPattern does Files.createDirectories then resolves databricks_jdbc.log inside), so a caller-supplied log FILE path is silently created as a directory and logs land at <path>/databricks_jdbc.log instead of being written verbatim

Context

• The behavior was first fixed in a DIFFERENT driver — reference PR: https://github.com/databricks/databricks-sql-kernel/pull/234 — which seeded the shared language-neutral spec. This issue tracks the same conformance gap in databricks/databricks-jdbc; the reference PR is for cross-referencing the intended behavior, NOT a change to this repo.
• Coverage PR carrying the reproducing xfail test(s): https://github.com/databricks/databricks-driver-test/pull/1224