GitHub user rxin opened a pull request:

    https://github.com/apache/spark/pull/8295

    [SPARK-10093][SPARK-10096][SQL] Avoid transformation on executors & fix 
UDFS on complex types

    This is kind of a weird case, but given a sufficiently complex query plan 
(in this case a TungstenProject with an Exchange underneath), we could have 
NPEs on the executors due to the time when we were calling 
transformAllExpressions
    
    In general we should ensure that all transformations occur on the driver 
and not on the executors. Some reasons for avoid executor side transformations 
include:
    
    * (this case) Some operator constructors require state such as access to 
the Spark/SQL conf so doing a makeCopy on the executor can fail.
    * (unrelated reason for avoid executor transformations) ExprIds are 
calculated using an atomic integer, so you can violate their uniqueness 
constraint by constructing them anywhere other than the driver.
    
    This subsumes #8285.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/rxin/spark SPARK-10096

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/8295.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #8295
    
----
commit e8b8240d389782bfc0e75cbe1797ce5aecc47092
Author: Michael Armbrust <[email protected]>
Date:   2015-08-18T20:19:39Z

    [SPARK-10093][SQL] Avoid transformation on executors.

commit acc1b4ad6c8615864ca723cc4c176dbed2c9aecc
Author: Reynold Xin <[email protected]>
Date:   2015-08-19T01:30:15Z

    Merge pull request #8285 from marmbrus/transformDriver
    
    [SPARK-10093][SQL] Avoid transformation on executors.

commit 836706bfe2d82e1bc4ce0019c490196ad975b72f
Author: Reynold Xin <[email protected]>
Date:   2015-08-19T01:37:15Z

    Added DataFrameComplexTypeSuite.

commit a3e4758950a5e3c1f686ffecf43d24f3456caad7
Author: Reynold Xin <[email protected]>
Date:   2015-08-19T01:38:03Z

    Updated documentation.

----


---
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]

Reply via email to