Yes that is what it looks like to me, but it's not hurting anything asis.  

-- 
Brock Noland
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)


On Thursday, November 29, 2012 at 6:23 PM, Roshan Naik wrote:

> you mean the corresponding classes need to be created ?
> 
> 
> On Thu, Nov 29, 2012 at 3:54 PM, Brock Noland <br...@cloudera.com> wrote:
> 
> > I actually don't think any of the classes exist an as such only basic
> > configuration checking is done. That is, the reference to the
> > non-existant class is not a problem but should be resolved in the long
> > run. I think this is the JIRA to resolve it:
> > 
> > https://issues.apache.org/jira/browse/FLUME-1051
> > 
> > Brock
> > 
> > On Thu, Nov 29, 2012 at 5:45 PM, Roshan Naik <ros...@hortonworks.com>
> > wrote:
> > > I see that some of the enum values in SourceConfigurationType refer to
> > 
> > non
> > > existent class names.
> > > Like for instance ...
> > > 
> > 
> > MULTIPORT_SYSLOGTCP("org.apache.flume.source.MultiportSyslogTCPSourceConfiguration")
> > > 
> > > and
> > > 
> > > EXEC("org.apache.flume.conf.source.ExecSourceConfiguration")
> > > 
> > > 
> > > It appears to me that they should be set to null like in the case of ...
> > > 
> > > SEQ(null)
> > > 
> > > If so i can go ahead and file a jira.
> > 
> > 
> > 
> > --
> > Apache MRUnit - Unit testing MapReduce -
> > http://incubator.apache.org/mrunit/
> > 
> 
> 
> 


Reply via email to