Hello.
I have an ETL app that appends to a JDBC table new results found at each
run. In 1.3.1 I did this:
testResultsDF.insertIntoJDBC(CONNECTION_URL + ";user=" + USER +
";password=" + PASSWORD, TABLE_NAME, false);
When I do this now in 1.4 it complains that the "object" 'TABLE_NAME'
already exists. I get this even if I switch the overwrite to true. I also
tried this now
testResultsDF.write().mode(SaveMode.Append).jdbc(CONNECTION_URL,
TABLE_NAME, connectionProperties);
getting the same error. It works running the first time creating the new
table and adding data successfully. But, running it a second time it (the
jdbc driver) will tell me that the table already exists (sorry, do not have
the full error msg anymore as I switched back to 1.3.1 to confirm that it
still worked there). Even SaveMode.Overwrite will give me the same error.
Has someone else seen this? Am I using the new API correctly? It seems
that the SaveModes are broken now. I saw a jira bug that talks about doing
wasteful introspections when the table exists, but this seems to be more
like a blocking regression.
Thanks and best regards,
Peter Haumer.
