You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Navina Ramesh (JIRA)" <ji...@apache.org> on 2016/01/11 21:43:39 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15092649#comment-15092649 ]
Navina Ramesh commented on SAMZA-852:
-------------------------------------
Hi [~vchekan] ,
Thanks for the pull request. However, Apache requires that we attach the patch to the JIRA. Hence, as a policy, we request contributors to attach the patch to the JIRA rather than provide a pull request.
For bigger code changes, you will also require a Review Board link to ease the review process.
If you can attach the patch here, I will be able to commit it.
Thanks!
> 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
> Priority: Minor
> Fix For: 0.10.1
>
>
> 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)