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 2017/09/19 21:29:00 UTC
[jira] [Resolved] (SAMZA-1416) Better logging around the exception
where class loading failed in initializing the SystemFactory for a
input/output system
[ https://issues.apache.org/jira/browse/SAMZA-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jake Maes resolved SAMZA-1416.
------------------------------
Resolution: Fixed
Fix Version/s: 0.14.0
Issue resolved by pull request 296
[https://github.com/apache/samza/pull/296]
> Better logging around the exception where class loading failed in initializing the SystemFactory for a input/output system
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: SAMZA-1416
> URL: https://issues.apache.org/jira/browse/SAMZA-1416
> Project: Samza
> Issue Type: Bug
> Reporter: Yi Pan (Data Infrastructure)
> Fix For: 0.14.0
>
>
> Currently, there is no log line showing the failure is on which system and which class name failed, when the config variable exists but is an empty string.
> {code}
> val systemFactories = systemNames.map(systemName => {
> val systemFactoryClassName = config
> .getSystemFactory(systemName)
> .getOrElse(throw new SamzaException("A stream uses system %s, which is missing from the configuration." format systemName))
> (systemName, Util.getObj[SystemFactory](systemFactoryClassName))
> }).toMap
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)