flume-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brock Noland <br...@cloudera.com>
Subject Re: Better sink/source/interceptor lists?
Date Wed, 08 Jan 2014 19:03:51 GMT
+1


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

> Hi,
>
> Do others think it would be valuable to Flume to:
>
> 1) more clearly list all available sources, sinks, interceptors
> Compare:
> http://flume.apache.org/FlumeUserGuide.html
> to:
> http://logstash.net/docs/1.3.2/ (scroll down a bit)
>
> 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.
>
> Thanks,
> Otis
> --
> Performance Monitoring * Log Analytics * Search Analytics
> Solr & Elasticsearch Support * http://sematext.com/
>
>
>
>


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

Mime
View raw message