FrankChen021 commented on PR #20036:
URL: https://github.com/apache/druid/pull/20036#issuecomment-5460436725

   Code-change explanation for mariadb-java-client 3.5.10 (verified at exact 
head e7dd5aad91c6e7d8dfcba5fb320d416f61e9f97c against upstream master 
9318bbee1a26e959b2526ac7cf7045dc906147f2):
   
   - The original dependency migration updates the MariaDB artifact/checksum 
and documentation, adapts URI parsing for Connector/J 3.x while retaining the 
legacy path, replaces the rejected Integer.MIN_VALUE streaming-fetch 
convention, recognizes both legacy and current packet exception classes, and 
keeps isolated 2.7.3 regression coverage.
   - The exact-head follow-up explicitly permits MariaDB 3.x’s canonical, 
case-sensitive `sslMode` property in `JdbcAccessSecurityConfig`; focused tests 
cover both `useSSL` and `sslMode`, and the default diagnostic plus 
configuration documentation are updated accordingly.
   - These source and test changes are required because Connector/J 3.x changed 
URI/property parsing, streaming-fetch behavior, exception classes, and its 
canonical TLS option. The allowlist remains exact rather than prefix-based, so 
unknown properties are still rejected.
   
   Focused verification: the original 32/32 migration tests and 15/15 new 
security/SQL/MySQL-input tests passed; affected-module Checkstyle and `git diff 
--check` passed.
   
   Backward compatibility: SAFE — both connector generations and TLS spellings 
are covered, Java 8 compatibility and licensing remain valid, no mandatory 
runtime transitives were added, and no Druid client/SPI, wire, serialization, 
persistence, or stored-data format changes.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to