[FLUME-1389] Flume gives opaque error if interceptor type not specified

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3.0
• Assignee: NO NAME
• Reporter: NO NAME
• Created: 23/Jul/12 00:34
• Updated: 01/Aug/12 00:10
• Resolved: 01/Aug/12 00:10

Description

If you declare an interceptor in the configuration but you don't specify the type, flume-agent dies with an opaque NPE. Instead it should die with a message warning that the interceptor doesn't have a type. You can see this using the following config file:

{{
receiver1.sources = gen
receiver1.sinks = null
receiver1.channels = ch1

receiver1.channels.ch1.type = memory

receiver1.sources.gen.type = seq
receiver1.sources.gen.channels = ch1

receiver1.sinks.null.type = null
receiver1.sinks.null.channel = ch1

receiver1.sources.gen.interceptors = int_a
}}

Result is:
{{
12/07/22 17:34:11 ERROR properties.PropertiesFileConfigurationProvider: Failed to load configuration data. Exception follows.
java.lang.NullPointerException
at org.apache.flume.interceptor.InterceptorBuilderFactory.lookup(InterceptorBuilderFactory.java:31)
at org.apache.flume.interceptor.InterceptorBuilderFactory.newInstance(InterceptorBuilderFactory.java:44)
at org.apache.flume.channel.ChannelProcessor.configureInterceptors(ChannelProcessor.java:104)
}}