Szehon Ho
Szehon Ho
thanks @huaxingao . By the way, do you know should the ```@since``` javadoc be at 4.0.0, or what version?
Rebase to try the test again
Do you think i need to have a separate update() call (or commit() call) to commit the change? What make me ask this is wondering whether we later add options()...
Added a separate update() call, to allow the possibility to have options() at some point in the UpdateWriter
OK thanks for checking. I had that originally, I can change it back. I guess we wont support something like this then (write options)? ``` spark.table("source") .update(Map("salary" -> lit(-1)), $"pk"...
Changed the api to be: ``` spark.table(tableNameAsString) .update(Map("salary" -> lit(-1))) .where($"pk" >= 2) .execute() ``` Can add option in a follow-up pr
@huaxingao @cloud-fan it makes sense, I made an attempt to move from DataFrame to SparkSession as suggested. I initially keep set() and where() API as it reads more like the...
Actually , updated the patch. Figured out I can use multiple case class (like MergeIntoWriter) to have compile time safety and SQL-like syntax, without the messy error checks. Thanks
Sqashed the commits to make rebase easier, but resolved the comments