The upstream release notes for 2.7.Final discuss setting the hibernate.dialect property to force the JDBC connector to use the MariaDB database dialect. This feature was added in DBZ-7874, however the property is not mentioned in the documentation. As Chris explained on Zulip,

... the hibernate.* namespace is very similar to the many Kafka Connect namespaces, it acts as a passthrough allowing the user to customize specific Hibernate behavior, including influencing which dialect will be chosen by Hibernate if it can not automatically resolve the dialect on its own.

We probably should note this passthrough somehow to help users know they can customize that behavior, even beyond just the dialect configuration.

... reference ... the fact that any additional hibernate configuration can be passed to the underlying Hibernate framework, if needed. We could specifically reference the hibernate.dialect in this as that's probably the most influential setting in the event that Hibernate has trouble resolving the target database's type and version.

The JDBC sink basically piggybacks off Hibernate's database resolution to overlay our own dialect atop of theirs.