[
https://issues.apache.org/jira/browse/SAMZA-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597877#comment-16597877
]
Yi Pan (Data Infrastructure) commented on SAMZA-1811:
-----------------------------------------------------
As a tentative solution, job planning logic are pulled out from
ApplicationRunner classes into JobPlanners (after PR 606). However, those
classes should eventually be consolidated into ExecutionPlanner, as an effort
to fix this ticket.
Some notes on the difference we have now between local and remote job
preparation from PR 606:
{quote}
Just to confirm, in future there will be just one implementation of
prepareStreamJobs, both for remote and local runner, right? Looks like the only
difference is run.id support and how they create streams.
{quote}
> Consolidate the ExecutionPlanner to handle both high-level DAG and low-level
> single node jobs
> ---------------------------------------------------------------------------------------------
>
> Key: SAMZA-1811
> URL: https://issues.apache.org/jira/browse/SAMZA-1811
> Project: Samza
> Issue Type: Improvement
> Reporter: Yi Pan (Data Infrastructure)
> Priority: Major
> Labels: fluent-api
>
> Currently, ExecutionPlanner only works for high-level DAG. It would be nice
> to consolidate the JobGraph generation and configuration generation between
> high-level DAG and low-level single-node jobs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
