That is a mistake, it's the 1.2.0 documentation. On Tue, Nov 13, 2012 at 2:02 PM, Rahul Ravindran <[email protected]> wrote: > The link below mentioned that it is the Flume 1.3 Snapshot guide and I > expected documentation regarding Spool Directory here. I did not see it. Am > I missing something? > > ________________________________ > From: Brock Noland <[email protected]> > To: [email protected] > Sent: Tuesday, November 13, 2012 10:12 AM > Subject: Re: high level plugin architecture > > Where are you seeing that? I see that documented in the 1.3.0 branch > under Spooling Directory Source > > > On Tue, Nov 13, 2012 at 11:57 AM, Rahul Ravindran <[email protected]> wrote: >> In the 1.3 snapshot documentation, I don't see anything about the spool >> directory source. Is that ready? >> >> Sent from my phone.Excuse the terseness. >> >> On Nov 13, 2012, at 9:43 AM, Hari Shreedharan <[email protected]> >> wrote: >> >> You can find the details of the components and how to wire them together >> here: http://flume.apache.org/FlumeUserGuide.html >> >> >> Thanks, >> Hari >> >> -- >> Hari Shreedharan >> >> On Tuesday, November 13, 2012 at 6:26 AM, S Ahmed wrote: >> >> Hello, >> >> So I downloaded the flume source, and I was hoping someone can go over the >> high-level plugin architecture. >> >> So each major feature of flume like a sink, or a channel has an interface, >> and then concrete implementations implement the interface. >> >> How exactly do you wireup the type of sink or channel you want to use, is >> it >> using IoC or do you just put the package/class in the config file and then >> it assumes your .jar is in the classpath? >> >> > > > > -- > Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/ > >
-- Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
