You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Brett Konold (Jira)" <ji...@apache.org> on 2020/05/23 07:36:00 UTC

[jira] [Updated] (SAMZA-2530) Split out processing logic from TaskSideInputStorageManager

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

Brett Konold updated SAMZA-2530:
--------------------------------
    Description: 
Currently TaskSideInputStorageManager conflates responsibility for two concepts:
 # managing StorageEngine instance for each side input store in the task
 # handling the processing of incoming envelopes

Splitting (2) out of TaskSideInputStorageManager will make delineation of responsibilities between classes more clear, and more closely match the pattern of class relationships already established by TaskStorageManager.

 

This is necessary to prevent TaskSideInputStorageManager from becoming a behemoth (like CSM is now) when introducing checkpointing functionality for side input SSPs.

  was:
Currently TaskSideInputStorageManager conflates responsibility for two concepts:
 # managing StorageEngine instance for each side input store in the task
 # handling the processing of incoming envelopes

Splitting (2) out of TaskSideInputStorageManager will make delineation of responsibilities between classes more clear, and more closely match the pattern of class relationships already established by TaskStorageManager.


> Split out processing logic from TaskSideInputStorageManager
> -----------------------------------------------------------
>
>                 Key: SAMZA-2530
>                 URL: https://issues.apache.org/jira/browse/SAMZA-2530
>             Project: Samza
>          Issue Type: Improvement
>            Reporter: Brett Konold
>            Priority: Major
>
> Currently TaskSideInputStorageManager conflates responsibility for two concepts:
>  # managing StorageEngine instance for each side input store in the task
>  # handling the processing of incoming envelopes
> Splitting (2) out of TaskSideInputStorageManager will make delineation of responsibilities between classes more clear, and more closely match the pattern of class relationships already established by TaskStorageManager.
>  
> This is necessary to prevent TaskSideInputStorageManager from becoming a behemoth (like CSM is now) when introducing checkpointing functionality for side input SSPs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)