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

Posted to commits@samza.apache.org by "Boris Shkolnik (JIRA)" <ji...@apache.org> on 2018/10/11 17:06:00 UTC

[jira] [Assigned] (SAMZA-1934) LocalApplicationRunner fails for LegacyTaskApplication app.class

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

Boris Shkolnik reassigned SAMZA-1934:
-------------------------------------

    Assignee: Boris Shkolnik

> LocalApplicationRunner fails for LegacyTaskApplication app.class
> ----------------------------------------------------------------
>
>                 Key: SAMZA-1934
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1934
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Boris Shkolnik
>            Assignee: Boris Shkolnik
>            Priority: Major
>
> For legacy job we set app.class to LegacyTaskApplication.
> It is being run by LocalApplicationRunner and it calls ApplicationUtils to instantiate the application. When it gets LegacyTaskApplication as the app.class, it tries to run newInstance on it, and as the result throws an exception (because there is no default constructor).
> I think we should check app.class, and if it is LegacyTaskApplication - treat it the same way as a blank app.class - create an object of LegacyTaskApplication type.
>  



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