[piyush15102003]

Summary

disable_frameworks_detection is documented as a driver property but had no DriverProperties entry, so buildFinalProperties forwarded it to client-v2. Since #2712 client-v2 rejects unknown keys, so setting the property (any value, URL or Properties form) failed the connection with Unknown and unmapped config properties. The flag was also read from the raw Properties argument before URL parameters were merged, so ?disable_frameworks_detection=true had no effect.

Changes:

• Add DriverProperties.DISABLE_FRAMEWORKS_DETECTION (default false), so the key stays on the driver side.
• Read the flag with isSet(...) after buildFinalProperties, so the URL and Properties forms behave the same.
• Correct the documented default in jdbc.mdx from true to false (detection is on when the key is not set).

Unchanged: other unknown keys are still forwarded to the client and rejected there, and detection stays on when the property is not set.

Closes #3218

Checklist

• Closes [jdbc-v2] Documented driver property disable_frameworks_detection makes the connection fail: Unknown and unmapped config properties #3218
• Unit tests covering the common scenarios were added (JdbcConfigurationTest: both forms, both values, unset, URL overriding Properties, unknown key still forwarded). The new cases fail on main and pass with the fix.
• A human-readable description of the changes was provided to include in CHANGELOG (history/latest/3218.md)

---

Note

Low Risk
Scoped JDBC configuration parsing fix with unit tests; behavior change is limited to a previously broken documented driver property.

Overview
Fixes JDBC V2 connections that failed when disable_frameworks_detection was set, because the key was forwarded to client-v2 as an unknown config and rejected.

The PR registers DriverProperties.DISABLE_FRAMEWORKS_DETECTION (default false) so the flag stays on the driver side, resolves it after URL and Properties are merged (URL wins over Properties), and updates jdbc.mdx so the documented default matches behavior. A changelog note and JdbcConfigurationTest cases cover URL vs properties, forwarding of unrelated unknown keys, and that this key is not passed to the client.

^{Reviewed by Cursor Bugbot for commit 8f5a88a. Bugbot is set up for automated code reviews on this repo. Configure here.}