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 2016/05/11 18:50:12 UTC

[jira] [Updated] (SAMZA-852) Better logging when system can not be created

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

Jake Maes updated SAMZA-852:
----------------------------
    Attachment: SAMZA-852_1.patch

> Better logging when system can not be created
> ---------------------------------------------
>
>                 Key: SAMZA-852
>                 URL: https://issues.apache.org/jira/browse/SAMZA-852
>             Project: Samza
>          Issue Type: Bug
>    Affects Versions: 0.10.0
>            Reporter: Vadim Chekan
>            Assignee: Jake Maes
>            Priority: Minor
>             Fix For: 0.10.1
>
>         Attachments: 0001-Inability-to-create-configured-producer-should-be-lo.patch, SAMZA-852_1.patch
>
>
> Inability to create configured producer should be logged as error. If not, it leads to unneeded investigation "why does it say system X can not be found, here it is!".
> Also, do not drop the original exception, it makes troubleshooting more difficult.
> My pull request: https://github.com/apache/samza/pull/8



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