spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <>
Subject [jira] [Commented] (SPARK-16026) Cost-based Optimizer framework
Date Tue, 16 Aug 2016 07:18:20 GMT


Sean Owen commented on SPARK-16026:

That's not OK in an Apache project. The discussion needs to at least be synced back to the
list regularly, not completed along with code offline. The problem is the code will arrive
with a "design discussion" that's a fait accompli. [~rxin] [~marmbrus] can you comment on
what is happening here?

> Cost-based Optimizer framework
> ------------------------------
>                 Key: SPARK-16026
>                 URL:
>             Project: Spark
>          Issue Type: New Feature
>          Components: SQL
>            Reporter: Reynold Xin
> This is an umbrella ticket to implement a cost-based optimizer framework beyond broadcast
join selection. This framework can be used to implement some useful optimizations such as
join reordering.
> The design should discuss how to break the work down into multiple, smaller logical units.
For example, changes to statistics class, system catalog, cost estimation/propagation in expressions,
cost estimation/propagation in operators can be done in decoupled pull requests.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message