Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/3637#issuecomment-66203211
The test failure reveals an issue in Spark SQL (ScalaReflection.scala:121
in schemaFor) where it gets confused if the case class includes multiple
constructors. The default behavior should probably be to take the constructor
with the most arguments, but I'll consult others about this. This PR may be on
temporary hold...
---
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
