Skip to content

Conversation

@rxin
Copy link
Contributor

@rxin rxin commented Jul 15, 2015

These traits are not super useful, and yet cause problems with toString in expressions due to the orders they are mixed in.

These traits are not super useful, and yet cause problems with toString in expressions due to the orders they are mixed in.
@marmbrus
Copy link
Contributor

Lgtm

@SparkQA
Copy link

SparkQA commented Jul 16, 2015

Test build #37422 has finished for PR 7433 at commit 1881f78.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds the following public classes (experimental):
    • abstract class LeafExpression extends Expression
    • abstract class UnaryExpression extends Expression
    • abstract class BinaryExpression extends Expression
    • abstract class BinaryNode extends LogicalPlan

@asfgit asfgit closed this in b064519 Jul 16, 2015
asfgit pushed a commit that referenced this pull request Jul 16, 2015
This builds on #7433 but also removes LeafNode/UnaryNode. These are slightly more complicated to remove. I had to change some abstract classes to traits in order for it to work.

The problem with LeafNode/UnaryNode is that they are often mixed in at the end of an Expression, and then the toString function actually gets resolved to the ones defined in TreeNode, rather than in Expression.

Author: Reynold Xin <[email protected]>

Closes #7434 from rxin/remove-binary-unary-leaf-node and squashes the following commits:

9e8a4de [Reynold Xin] Generator should not be foldable.
3135a8b [Reynold Xin] SortOrder should not be foldable.
9c589cf [Reynold Xin] Fixed one more test case...
2225331 [Reynold Xin] Aggregate expressions should not be foldable.
16b5c90 [Reynold Xin] [SPARK-9085][SQL] Remove LeafNode, UnaryNode, BinaryNode from TreeNode.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants