[ 
https://issues.apache.org/jira/browse/SAMZA-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Riccomini updated SAMZA-73:
---------------------------------

    Description: 
This is an exploratory ticket to figure out if we want to support topologies in 
Samza.

Potential solutions include:

1. Don't support them as part of the framework (a la Hadoop).
2. Use Tez as topology runner.
3. Use config inheritence (.properties file merging). This already exists.
4. Write some kind of JobGroupRunner that executes multiple jobs at one time.
5. ?

There are probably a lot of solutions. Some goals of this ticket are:

a. Config sharing between job with a lot of the same config.
b. Whether we want to run multiple jobs with a single AM (in YARN).
c. How to start/stop only a subset of job when running in a topology.



  was:
This is an exploratory ticket to figure out if we want to support topologies in 
Samza.

Potential solutions include:

1. Don't support them as part of the framework (a la Hadoop).
2. Use Tez as topology runner.
3. Use config inheritence (.properties file merging). This already exists.
4. ?

There are probably a lot of solutions. Some goals of this ticket are:

a. Config sharing between job with a lot of the same config.
b. Whether we want to run multiple jobs with a single AM (in YARN).
c. How to start/stop only a subset of job when running in a topology.




> Add topologies to Samza
> -----------------------
>
>                 Key: SAMZA-73
>                 URL: https://issues.apache.org/jira/browse/SAMZA-73
>             Project: Samza
>          Issue Type: Wish
>          Components: build, container, yarn
>    Affects Versions: 0.6.0
>            Reporter: Chris Riccomini
>              Labels: project
>
> This is an exploratory ticket to figure out if we want to support topologies 
> in Samza.
> Potential solutions include:
> 1. Don't support them as part of the framework (a la Hadoop).
> 2. Use Tez as topology runner.
> 3. Use config inheritence (.properties file merging). This already exists.
> 4. Write some kind of JobGroupRunner that executes multiple jobs at one time.
> 5. ?
> There are probably a lot of solutions. Some goals of this ticket are:
> a. Config sharing between job with a lot of the same config.
> b. Whether we want to run multiple jobs with a single AM (in YARN).
> c. How to start/stop only a subset of job when running in a topology.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to