This is cool, thanks! AccumuloSink.eventsProcessed variable is never read.
-Eric On Mon, Jul 15, 2013 at 3:13 PM, Matthew Molek <[email protected]>wrote: > No, not intentional. Thanks for pointing that out. This code is a bit of a > work in progress still. > > Everything works, but you're right that the exception handling is not > robust yet. > > > > > On Mon, Jul 15, 2013 at 2:57 PM, Keith Turner <[email protected]> wrote: > > > I took a quick look at the code. In AccumuloSink the configure() and > > start() methods catch exceptions and just print stack traces. Is that > > intentional, or is it a work in progress? > > > > > > On Mon, Jul 15, 2013 at 2:03 PM, Matthew Molek <[email protected] > > >wrote: > > > > > The idea of a writing flume sink for accumulo was suggested last year > in > > > ACCUMULO-811, but I don't think any activity ever came of it. > > > > > > https://issues.apache.org/jira/browse/ACCUMULO-811 > > > > > > I've rewritten the original code (which wasn't on the Jira, but I got a > > > copy of) to mirror the way the flume sink for hbase is organized, and > to > > > work with flume-ng. > > > > > > My code is up on github: > > https://github.com/mpmolek/flume-ng-accumulo-sink > > > > > > I'd welcome any comments, and if there is interest, I'd be happy to > have > > > this added to contrib. > > > > > > -Matt > > > > > > -- > > > This communication is the property of ClearEdge IT Solutions, LLC and > > may > > > contain confidential and/or privileged information. Any review, > > > retransmissions, dissemination or other use of or taking of any action > in > > > reliance upon this information by persons or entities other than the > > > intended recipient is prohibited. If you receive this communication in > > > error, please immediately notify the sender and destroy all copies of > the > > > communication and any attachments. > > > > > > > -- > This communication is the property of ClearEdge IT Solutions, LLC and may > contain confidential and/or privileged information. Any review, > retransmissions, dissemination or other use of or taking of any action in > reliance upon this information by persons or entities other than the > intended recipient is prohibited. If you receive this communication in > error, please immediately notify the sender and destroy all copies of the > communication and any attachments. >
