java.sql.SQLException : Unknown system variable 'OPTION' 异常

Question

我正在使用 Ambari 服务器安装 MYSQL，以便在 ubuntu 上安装 hadoop。

我从 Xampp 安装了 My Sql，并且工作正常。

My SQL 5.6版本去掉了set`Option关键字，mariaDB(xampp自带)与之一致。

网站显示兼容MySQL 5.6版本，应该没问题。

回应the only relevant link I found ,

当我检查我的 sql 版本时:

mysql -v
The program 'mysql' can be found in the following packages:
 * mysql-client-core-5.6
 * mariadb-client-core-10.0

这就是我得到的。我相信链接中提到的问题不是这里的情况吗？

当我尝试向 ambari 服务器注册我的主机时，它会抛出此错误:

我已尝试更换连接器、版本和一切可能的东西。但我不断收到此错误。

java.sql.SQLException: Unknown system variable 'OPTION'
    at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:946)
    at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2985)
    at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1631)
    at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1723)
    at com.mysql.jdbc.Connection.execSQL(Connection.java:3277)
    at com.mysql.jdbc.Connection.unsetMaxRows(Connection.java:5867)
    at com.mysql.jdbc.Statement.realClose(Statement.java:2070)
    at com.mysql.jdbc.PreparedStatement.realClose(PreparedStatement.java:2204)
    at com.mysql.jdbc.PreparedStatement.close(PreparedStatement.java:695)
    at com.mchange.v1.db.sql.StatementUtils.attemptClose(StatementUtils.java:41)
    at com.mchange.v2.c3p0.stmt.GooGooStatementCache.synchronousDestroyStatement(GooGooStatementCache.java:413)
    at com.mchange.v2.c3p0.stmt.GooGooStatementCache.closeAll(GooGooStatementCache.java:351)
    at com.mchange.v2.c3p0.impl.NewPooledConnection.closeAllCachedStatements(NewPooledConnection.java:598)
    at com.mchange.v2.c3p0.impl.NewPooledConnection.close(NewPooledConnection.java:468)
    at com.mchange.v2.c3p0.impl.NewPooledConnection.close(NewPooledConnection.java:191)
    at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.destroyResource(C3P0PooledConnectionPool.java:470)
    at com.mchange.v2.resourcepool.BasicResourcePool$1DestroyResourceTask.run(BasicResourcePool.java:964)
    at com.mchange.v2.async.ThreadPoolAsynchronousRunner

Answer 1

我有同样的问题，更新 mysql 驱动程序版本修复了它。