You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "eaton (JIRA)" <ji...@apache.org> on 2017/08/22 08:55:00 UTC

[jira] [Created] (SPARK-21807) The getAliasedConstraints function in LogicalPlan will take a long time when number of expressions is greater than 100

eaton created SPARK-21807:
-----------------------------

             Summary: The getAliasedConstraints function  in LogicalPlan will take a long time when number of expressions is greater than 100 
                 Key: SPARK-21807
                 URL: https://issues.apache.org/jira/browse/SPARK-21807
             Project: Spark
          Issue Type: Improvement
          Components: SQL
    Affects Versions: 2.2.0
            Reporter: eaton


The getAliasedConstraints  fuction in LogicalPlan.scala will clone the expression set when an element added,
and it will take a long time.
Before modified, the cost of getAliasedConstraints is:
100 expressions:  41 seconds
150 expressions:  466 seconds



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org