I was expecting to get the same results with both:
dataFrame.write.mode(SaveMode.Overwrite).jdbc(dbUrl, "my_table", props)
and
dataFrame.write.mode(SaveMode.Overwrite).format("jdbc").options(opts).option("dbtable",
"my_table")
In the first example, it behaves as expected. It creates a new tabl
Hi, Dragisa,
Your second way is incomplete, right? To get the error you showed, you need
to put save() there.
Yeah, we can implement the trait CreatableRelationProvider for JDBC. Then,
you will not see that error.
Will submit a PR for that.
Thanks,
Xiao
2016-07-06 10:05 GMT-07:00 Dragisa Krs
Yes, I had the save() at the end. I truncated example to highlight the
difference and forgot to put back the save()
It would be great to have the same behavior (and same code used) for both
jdbc() and format("jdbc").
Thank you.
On Wed, Jul 6, 2016 at 10:21 AM, Xiao Li wrote:
> Hi, Dragisa,
>
>
HI Buddy,
I sued both but DataFrame.write.jdbc is old, and will work if provide
table name , It wont work if you provide custom queries . Where
as DataFrame.write.format is more generic as well as working perfectly with
not only table name but also custom queries . Hence I recommend to use
the
Hi, Dragisa,
Just submitted a PR for implementing the save API.
https://github.com/apache/spark/pull/14077
Let me know if you have any question,
Xiao
2016-07-06 10:41 GMT-07:00 Rabin Banerjee :
> HI Buddy,
>
>I sued both but DataFrame.write.jdbc is old, and will work if provide
> table nam
