Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
3.0.3, 3.0.4
-
None
-
None
Description
The release notes for Connector-J 3.0.3 mention that some connection options have been removed, with comments/explanations and a few suggested replacements. However, the general documentation for Connector-J is not updated as of today and still shows the old parameters as being valid for the latest release.
Note that this issue is made worse by the fact that the driver does not throw when passing unrecognized options, they merely remain in Configuration.nonMappedOptions(). Thus, users could be very confused when they pass the options described in the documentation but they do not take effect.
At least the following parameters are misdocumented:
- New, missing documentation: (that I know of)
- sslMode, which replaces a set of other properties that are still accepted
- timezone
- Removed, still in documentation:
- allowMasterDownConnection
- assureReadOnly
- autoReconnect
- cachePrepStmts
- callableStmtCacheSize
- enablePacketDebug
- failoverLoopRetries
- jdbcCompliantTruncation
- keyPassword
- loadBalanceBlacklistTimeout
- log
- passwordCharacterEncoding
- prepStmtCacheSqlLimit
- profileSql
- retriesAllDown
- rewriteBatchedStatements
- serverTimezone
- sharedMemory
- slowQueryThresholdNanos
- staticGlobal
- tcpNoDelay
- tcpRcvBuf
- tcpSndBuf
- trackSchema
- trustStore
- trustStorePassword
- trustStoreType
- useBatchMultiSend
- useBatchMultiSendNumber
- useFractionalSeconds
- useOldAliasMetadataBehavior
- validConnectionTimeout