[
https://issues.apache.org/jira/browse/SAMZA-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346049#comment-16346049
]
Jake Maes commented on SAMZA-1580:
----------------------------------
Ok cool.
My past experience with planners always had a simple pattern:
query -> planner -> queryPlan
And the planner encapsulated all the steps to get from the query to the plan.
In our case, I was thinking
application -> planner -> executionPlan
There may be advantages to doing it another way, but I've only seen it this
way.
My 2 cents...
> Optimizer for High-level API
> ----------------------------
>
> Key: SAMZA-1580
> URL: https://issues.apache.org/jira/browse/SAMZA-1580
> Project: Samza
> Issue Type: Bug
> Reporter: Xinyu Liu
> Assignee: Xinyu Liu
> Priority: Major
>
> Need an optimizer before the planning, which does the following:
> 1) Replace partitionBy() with a map(keyFn, ValueFn) if task count = 1
> 2) Remove broadcast() if task count = 1.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
