[
https://issues.apache.org/jira/browse/FLUME-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452567#comment-13452567
]
Hudson commented on FLUME-1480:
-------------------------------
Integrated in flume-trunk #297 (See
[https://builds.apache.org/job/flume-trunk/297/])
FLUME-1480: Replace object descriptor with detailed component type plus
name (Revision 04c2de49522e6d66c3c2a199f8ed667b40a67534)
Result = FAILURE
brock :
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=04c2de49522e6d66c3c2a199f8ed667b40a67534
Files :
* flume-ng-core/src/main/java/org/apache/flume/source/AbstractSource.java
* flume-ng-core/src/main/java/org/apache/flume/channel/AbstractChannel.java
* flume-ng-core/src/main/java/org/apache/flume/sink/AbstractSink.java
> Replace object descriptor with detailed component type plus name
> ----------------------------------------------------------------
>
> Key: FLUME-1480
> URL: https://issues.apache.org/jira/browse/FLUME-1480
> Project: Flume
> Issue Type: Improvement
> Components: Easy
> Affects Versions: v1.2.0
> Reporter: Denny Ye
> Assignee: Ted Malaska
> Priority: Minor
> Fix For: v1.3.0
>
> Attachments: FLUME-1480-0.patch
>
>
> I am tracking issue at dynamic configuration. And there have many logs with
> object descriptor like this:
> {quote}
> org.apache.flume.channel.MemoryChannel@594ab51b
> org.apache.flume.sink.DefaultSinkProcessor@488ddb93
> org.apache.flume.lifecycle.LifecycleSupervisor$SupervisorPolicy$AlwaysRestartPolicy@1cad6513
> {quote}
> It's really hard to identify in which component from log record. Specially, I
> would like to know the primary concrete component type (Source, Channel or
> Sink) and component name (mc, hsa,...)
--
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
