[
https://issues.apache.org/jira/browse/FLUME-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brock Noland updated FLUME-1274:
--------------------------------
Fix Version/s: (was: v1.3.0)
v1.4.0
> Clarify semantics of uncaught runtime exceptions thrown from configure()
> method
> -------------------------------------------------------------------------------
>
> Key: FLUME-1274
> URL: https://issues.apache.org/jira/browse/FLUME-1274
> Project: Flume
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: v1.1.0
> Reporter: Mike Percy
> Priority: Minor
> Fix For: v1.4.0
>
>
> In FLUME-1273, I thought we may not be handling exceptions coming out of
> configure() in Configurable components very well. In actuality, the behavior
> is arguably quite sane. But we should indicate what the implications are in
> an error message printed to the Flume log, and ideally make the call depth
> between throw and catch a little less deep, for maintainability / clarity's
> sake.
> The error message in the log could look something like:
> ERROR: Exception thrown while attempting to configure component "<foo>".
> Flume agent will not be started. Exception follows.
> ... stack trace ...
--
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
