Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7176#issuecomment-118227724
After spending some time working with this, I'm thinking that we should
back out of the use of ScalaCheck for now. I seem to be running into a lot of
difficulties with getting it to work well with some of our existing
SparkPlanTest assertions, which fail by throwing exceptions, and also ran into
some corner-cases with nulls. It's _possible_ to use it to write the style of
test that I want, but I worry that the resulting test code is going to be
really hard to understand / contribute to.
I'm going to roll back that part of the changes and will use my old custom
implementation instead. We can revisit ScalaCheck generators for SQL rows
later.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
