[
https://issues.apache.org/jira/browse/FLUME-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858549#comment-13858549
]
Joshua Hyde commented on FLUME-2284:
------------------------------------
Not to try and push anyone, but what's a decent ETA on knowing if this is
rejected or approved and, in the case of the latter, released? We're going to
be doing some heavy investing into Flume at my work this quarter, and I was
hoping to use this to try and test some of the work we'll be doing.
If that's too aggressive of a timeline for your release cycle, I can go the
route of releasing this for now through the Sonatype OSS process, but I'd
rather not risk fragmentation/pollution of the central repo with two copies of
this work if the next version of Flume will include this change and come out
soon enough for our needs. :)
> Accept submission of HTTP server sink
> -------------------------------------
>
> Key: FLUME-2284
> URL: https://issues.apache.org/jira/browse/FLUME-2284
> Project: Flume
> Issue Type: Improvement
> Reporter: Joshua Hyde
> Attachments: flume-2284.2013-12-26.1042.diff
>
>
> I've written a Flume sink that exposes the events it receives via an HTTP
> server:
> https://github.com/jrh3k5/flume-http-server-sink
> This helps in integration testing of sources and channels that a developer
> may write for themselves. I'd like to make this part of the official Flume
> platform. What are the guidelines for submitting code like this? I'm afraid I
> wasn't able to find any guidelines on the Flume site itself.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)