Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/8226#issuecomment-132076896
As we cannot tell what downstream operator is inside of the spark plan
operator, it's hard to tell if it's really an optimization. JoinedRow is used
here for reducing the memory copying or object creation , but this PR does
creates small objects and copying memory when constructing new UnsafeRow, right?
I'll agree if we can move the logic into `SparkStrategy`, what do you think?
---
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]
