I do spend a lot of time scrolling around...even a framebar would help, or a "back to top" link in each section...but a table would be nice, and a wishlist would be great.

Devin Suiter
Jr. Data Solutions Software Engineer
100 Sandusky Street | 2nd Floor | Pittsburgh, PA 15212
Google Voice: 412-256-8556 | www.rdx.com

On Wed, Jan 8, 2014 at 2:03 PM, Brock Noland <brock@cloudera.com> wrote:

On Wed, Jan 8, 2014 at 12:56 PM, Otis Gospodnetic <otis.gospodnetic@gmail.com> wrote:

Do others think it would be valuable to Flume to:

1) more clearly list all available sources, sinks, interceptors

I find the Logstash "table" of inputs, codecs, filters, and outputs MUCH easier to read and it quickly gives me an idea of what Logstash can handle.  I can't do that with Flume without a ton of scrolling up and down.

Related: there is https://cwiki.apache.org/confluence/display/FLUME/Flume+NG+Plugins . Looks kind of secondary, very outdated, hidden (found it via Google)
Considering the support for inputs/outputs/filters is one of the key things people look when comparing Flume to Fluentd, Logstash, or even syslog, shouldn't this stuff be much more prominently displayed and nicely organized?

2) on a Wiki, create a sources/sinks/interceptors/... wishlist so potential contributors know what they could work on, esp. if it scratches their itch?  JIRA could be used for this, too, but JIRA is often slow and not a great fit for this.

Performance Monitoring * Log Analytics * Search Analytics
Solr & Elasticsearch Support * http://sematext.com/

Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org