Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/21083
@cloud-fan the approach itself seems OK to me. Indeed, I prefer this one
over the previous status where we had `constraints` enforced on the output and
`allConstraints` containing also the others: I think it was pretty confusing
and I think that moving those additional constraints to the optimizer is the
right thing to do. Anyway, I will review it more carefully in the next days,
asap.
As far as the credit is regarded, there is no issue for me. You can give
credit to @maryannxue and @KaiXinXiaoLei.
I think I can close #20717 then, since it is going to be covered here, am I
right?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
