Ralph, If FailoverAppender could do that, that would be ideal.
Thanks for your time. Yogi On Thu, Feb 14, 2013 at 10:52 AM, Ralph Goers <[email protected]>wrote: > What you are asking for is essentially the Flume embedded appender. > However, since Flume has so many dependencies I could understand why you > would want to do this. > > Would making RollingFileAppender not be final actually buy you anything? > You would have to provide your own PluginFactory method and constructor no > matter what you do and that only leaves you the append, getFileName and > getFilePattern methods, which are all trivial. > > That said, I have a need to have the FailoverAppender be able to failover > from the FlumeAppender to some sort of file appender and then have the > events in that file get routed back through Flume when it becomes > available. I haven't thought of how to implement that as it is complicated. > > Ralph > > > On Feb 14, 2013, at 9:58 AM, Yogi Nerella wrote: > > > Hi, > > > > I would like to have a RollingFlumeAppender built on top of > > RollingFileAppender, so that all synchronous operations are written to > the > > local file system, and on file rolled trigger, FlumeAppener will pickup > the > > job and send the generated file to the Flume Agent? > > > > Currently RollingFileAppender is Final ? Is there any reason for it be > > final? Why cant we extend RollingFileAppender? > > > > Thanks for the help, > > Yogi > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
