Hi, Does anyone know if its feasible to consider making Spark's "insert overwrite" implement serializable transaction, like delete, update, merge?
Maybe at least for "overwrite by filter", then it can narrow down the conflict checks needed on the commitWithSerializableTransaction side. I don't have the full context on the Spark side if its feasible to do the rewrite as Delete/Merge/Update does, to use this mechanism. Its for a use-case like "insert overwrite into table foo partition (date=...) select ... from foo", which I understand is not the common use case for insert overwrite, as its usually select from another table. Thanks in advance, Szehon
