Github user dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/11521#issuecomment-192493088
@cloud-fan I really like your second approach, which is much cleaner and
simpler, but
I was wondering how it helps with our current problem ? In my understanding
the problem
is that plan->transformExpression is considering the productIterator as
input which
includes the genertor's output attributes and we end up resolving these
attributes
from child's output.
Just trying learn from you and improve my understanding :-)
---
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]
