Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/4039#issuecomment-71537019
The sole purpose of adding `SpecificMutableRow` is to avoid boxing cost, so
using `boxed` here doesn't sound good. For SPARK-5236, schema mismatch can
often produce similar exceptions. @alexbaretta Would you please add a snippet
that helps reproducing this issue in the JIRA ticket description? I guess the
root cause hides elsewhere.
---
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
