Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
This is the ticket to track the work for application runtime API class changes s.t. user applications written in high- or low-level applications can be created and launched via the same set of standard API methods in YARN and standalone environments.
Attachments
Issue Links
- blocks
-
SAMZA-1818 TestRunner should consolidate all constructor to use SamzaApplication and config
- Closed
- Dependent
-
SAMZA-1839 Cleanup the old constructors of StreamProcessor
- Open
- is a parent of
-
SAMZA-1168 Migrate yarn local runner to use StreamProcessor
- Open
-
SAMZA-1830 TestRepartitionJoinWindowApp should call runner.status() to determine whether the test is successful or not
- Open
-
SAMZA-1832 Race condition between SamzaContainerListener.onContainerFailure(t) and StreamProcessor.stop()
- Resolved
-
SAMZA-1811 Consolidate the ExecutionPlanner to handle both high-level DAG and low-level single node jobs
- Open
-
SAMZA-1833 StreamProcessor should not implicitly create JobCoordinator in the constructor
- Open
-
SAMZA-1818 TestRunner should consolidate all constructor to use SamzaApplication and config
- Closed
-
SAMZA-1835 Consolidate all processorId generation code to StreamProcessor
- Closed
- is related to
-
SAMZA-1819 Deprecate ThreadJobFactory and ProcessJobFactory
- Open
- relates to
-
SAMZA-1813 ApplicationRunner should use Planner generated configs for StreamManager
- Resolved
-
SAMZA-1834 Too many IDs for processors in Samza
- Open
-
SAMZA-1842 Need consistent logic to calculate input, output, and intermediate streams in high and low-level API applications
- Open
- links to
- mentioned in
-
Page Loading...