Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Flume >> mail # user >> Better sink/source/interceptor lists?


Copy link to this message
-
Re: Better sink/source/interceptor lists?
I think in the past we have prefered docs over wiki.  I agree with that
sentiment.  However, I don't see why we have to have all of our docs in a
single page....and generally I think your suggestions are good.
On Wed, Jan 8, 2014 at 3:00 PM, Otis Gospodnetic <[EMAIL PROTECTED]
> wrote:

> Thanks for positive and quick feedback.
>
> I'd imagine you'd really just want to:
> * migrate docs to wiki
> * have page-per-sink and page-per-source and page-per-....
> * toc and/or sidebar for easy navigation
> * wiki..... easy for others to add their own plugins
>
> Anyhow, just wanted to provide this outside view feedback.  Hopefully
> somebody from the Flume team thinks this is important enough to actually do
> it. :)
>
> Otis
> --
> Performance Monitoring * Log Analytics * Search Analytics
> Solr & Elasticsearch Support * http://sematext.com/
>
>
> On Wed, Jan 8, 2014 at 2:07 PM, Devin Suiter RDX <[EMAIL PROTECTED]> wrote:
>
>> 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 <[EMAIL PROTECTED]> wrote:
>>
>>> +1
>>>
>>>
>>> On Wed, Jan 8, 2014 at 12:56 PM, Otis Gospodnetic <
>>> [EMAIL PROTECTED]> 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
>>>
>>
>>
>
--
Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org