[
https://issues.apache.org/jira/browse/FLUME-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535569#comment-13535569
]
Hudson commented on FLUME-1795:
-------------------------------
Integrated in flume-trunk #343 (See
[https://builds.apache.org/job/flume-trunk/343/])
FLUME-1795: Flume thrift legacy source does not have proper logging
configured (Revision 3369b34320175fc9b1132ef3e1ac8551ae55492a)
Result = SUCCESS
brock :
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=3369b34320175fc9b1132ef3e1ac8551ae55492a
Files :
*
flume-ng-legacy-sources/flume-thrift-source/src/test/resources/log4j.properties
> Flume thrift legacy source does not have proper logging configured
> ------------------------------------------------------------------
>
> Key: FLUME-1795
> URL: https://issues.apache.org/jira/browse/FLUME-1795
> Project: Flume
> Issue Type: Bug
> Components: Test
> Environment: All
> Reporter: Venkat Ranganathan
> Assignee: Venkat Ranganathan
> Priority: Minor
> Fix For: v1.4.0
>
> Attachments: Flume-1795.patch
>
>
> The lack of proper logging configuration makes investigating bugs (see
> Flume-1788) very difficult and time consuming to debug. That bug is a
> special case as it involves low level scheduling issues
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
