Uploaded image for project: 'Apache Nemo'
  1. Apache Nemo
  2. NEMO-235

Refactor TaskExecutor's data processing logic

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.1

      Description

      TaskExecutor has complex logic to process data, additional output, side inputs and so on. This is because the TaskExecutor manages data flow within a Task. The downside of this approach is that it increases complexity of TaskExecutor if we add other feature of data (e.g., watermark) and it transfers data between Transform by pull-based approach, which may occur additional enqueue/dequeue overhead for each element processing. 

       

      We can simplify the TaskExecutor's data processing logic and implement push-based element processing by delegating the data flow in a Task to OutputCollector. We can implement various OutputCollectors such as push-based output collector that emits data to downstream operator directly and sink output collector that writes data to Writer. 

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                taegeonum Tae-Geon Um
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: