Github user ilganeli commented on the issue:
https://github.com/apache/spark/pull/16685
I recognize that this is not an optimal solution, but Spark has
historically contained multiple sub-optimal operations that are nonetheless
useful in certain contexts and it's left to the user to understand and use
things correctly. A few examples off the top of my head include
collectPartitions, zipWithIndex, and repartition - all of which may be
expensive operations but are nonetheless useful when used appropriately.
I believe there's value in introducing this as a starting point which works
in most scenarios and is more efficient than relying on the database to handle
the uniqueness constraint and be responsible for a mass update, with the
expectation of future improvement.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
