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

Posted to commits@samza.apache.org by "Jake Maes (JIRA)" <ji...@apache.org> on 2018/01/12 19:27:05 UTC

[jira] [Updated] (SAMZA-1223) User-facing class ApplicationRunner should not expose getStreamSpec()

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

Jake Maes updated SAMZA-1223:
-----------------------------
    Fix Version/s:     (was: 0.14.0)
                   0.15.0

> User-facing class ApplicationRunner should not expose getStreamSpec()
> ---------------------------------------------------------------------
>
>                 Key: SAMZA-1223
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1223
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Jake Maes
>             Fix For: 0.15.0
>
>
> This method:
> https://github.com/apache/samza/blob/4bf8ab6ebdf95cdf78f07b81a3b450a7f3fd9d45/samza-api/src/main/java/org/apache/samza/runtime/ApplicationRunner.java#L125
> has no place in a "runner". It's arguable that it should belong in a RuntimeEnvironment or StreamConfig or other, but since ApplicationRunner is user-facing, we need to get it out of there before the release.
> From our discussion, the two best options are:
> 1. Push it down to StreamConfig
> 2. Make it private



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)