Paul Wu created SPARK-19296:
-------------------------------
Summary: Awkward changes for JdbcUtils.saveTable in Spark 2.1.0
Key: SPARK-19296
URL: https://issues.apache.org/jira/browse/SPARK-19296
Project: Spark
Issue Type: Bug
Components: SQL
Affects Versions: 2.1.0
Reporter: Paul Wu
Priority: Minor
The Change from JdbcUtils.saveTable(DataFrame, String, String, Property) to
JdbcUtils.saveTable(DataFrame, String, String, JDBCOptions), not only
incompatible to previous versions (so the previous code in java won't compile,
but also introduced silly code change: One has to specify url and table twice
like this:
JDBCOptions jdbcOptions = new JDBCOptions(url, table, map);
JdbcUtils.saveTable(ds, url, table,jdbcOptions);
Why does one have to supply the same things ulr, table twice? (If you don't
specify it in both places, the exception will be thrown).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
