I've been using MariaDB since 5.2.4 for everyone of my side projects without issues. But having a problem while playing with Tungsten Replicator based replication.
Logged a bug report at http://code.google.com/p/tungsten-replicator/issues/detail?id=256 and the Tungsten Replicator folks say it could be possibly a problem with newer MariaDB 5.2.9 release ?
Not sure who I should be contacting or whether or not MariaDB folks have already been made aware of this issue ?
Answer Answered by elenst in this comment.
The investigation has shown that the problem does not occur with an up-to-date version of drizzle-jdbc. Recent Tungsten packages, e.g. 2.0.5-426, contain drizzle-jdbc-0.91-SNAPSHOT, while the current version is 1.1.
The old version of drizzle-jdbc was incorrectly setting CLIENT_PLUGIN_AUTH bit in the handshake packet, without actually supporting pluggable auth. It has been fixed in 1.1.