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

Posted to commits@samza.apache.org by "Jagadish (JIRA)" <ji...@apache.org> on 2016/03/17 21:45:33 UTC

[jira] [Updated] (SAMZA-901) SamzaAppState re-design for thread safety

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

Jagadish updated SAMZA-901:
---------------------------
    Summary: SamzaAppState re-design for thread safety  (was: SamzaAppState re-design)

> SamzaAppState re-design for thread safety
> -----------------------------------------
>
>                 Key: SAMZA-901
>                 URL: https://issues.apache.org/jira/browse/SAMZA-901
>             Project: Samza
>          Issue Type: Sub-task
>            Reporter: Jagadish
>
> There are a bunch of state data structures that are publicly exposed in SamzaAppState. These must be made thread-safe into accessors. These public global variables could mutated everywhere in Samza without regard for safety/visibility or correctness. 
> Making the SamzaAppState thread-safe will fix these potential races in code. Also, as Samza evolves, it is useful to provide accessors instead of exposing all the public variables.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)