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

Posted to commits@samza.apache.org by "Viktor (JIRA)" <ji...@apache.org> on 2019/02/22 12:52:00 UTC

[jira] [Commented] (SAMZA-1935) Refactor TaskContextImpl to not include access to objects that are only used internally

    [ https://issues.apache.org/jira/browse/SAMZA-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775102#comment-16775102 ] 

Viktor commented on SAMZA-1935:
-------------------------------

Hello, we are 5 students working on this problem and I would like to register as an assignee. (it is specified in our assignment that we should be registered as an assignee)

> Refactor TaskContextImpl to not include access to objects that are only used internally
> ---------------------------------------------------------------------------------------
>
>                 Key: SAMZA-1935
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1935
>             Project: Samza
>          Issue Type: Improvement
>            Reporter: Cameron Lee
>            Priority: Major
>
> TaskContext is intended as a public API, but TaskContextImpl has been used to pass around objects for internal usage as well (e.g. stream metadata cache, object registry). Some internal components cast the TaskContext to a TaskContextImpl to access these objects, but that is not an ideal pattern.
> One consideration is to split this internal functionality into a separate object which is only passed around internally and is decoupled from TaskContextImpl.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)