Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/17902
I don't think it's worth it to call out every design decision here. The
feature set exists because it will be used by the code in the subsequent
milestones; so if reviewing this you either need a bit of faith that there's a
good reason for the feature to exist, or you need to go check out the rest of
the code, which is why I posted a link to it in my first comment.
Again, feel free to ask specific questions. But don't be surprised if the
answer is "it will be used in a subsequent milestone".
The reason for this is because I don't want to send a single PR that has >
20k line changes. Nobody is going to review that.
> Will there be intermittent SQL test failures until that is checked in?
No, as you can see, tests pass.
---
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
