Attila thank you so much for your responses. Ended up getting me in the
right direction and I fixed the issue. It turns out that EMR installs
mariadb connectors in the java installation of the server. After removing
those the import started working.
Any ideas why the mariadb connector would take precedence over the mysql
one? It seems like this would be outside of the control of Sqoop. I was
taking a look at the sqoop code and when specifying --driver and no manager
it's going to use the GenericJdbcManager so would end up using whatever was
handling the jdbc:mysql connection strings. Since mariadb connector was in
the java installation I guess that takes precedence. If I specify both
--driver and --connection-manager it blows up because the MysqlManager
doesn't have the appropriate constructor. Specifying just the manager looks
like it would force it to use the MysqlManager which would end up doing a
Class.forName("com.mysql.jdbc.Driver"). Seems like this isn't enough to
make it use the Mysql connector?
Thanks,
Geren
