You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Jeff Guilmard (JIRA)" <ji...@apache.org> on 2014/11/28 19:43:12 UTC

[jira] [Updated] (FLUME-2524) Adding an HTTP Sink

     [ https://issues.apache.org/jira/browse/FLUME-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Guilmard updated FLUME-2524:
---------------------------------
    Attachment: FLUME-2524-1.patch

New patch, replacing the first one.

This patch looks stable to me. It improves a lot the performances, which was a major work in order to tune HttpClient.
It adds also the monitoring part that was missing.

This version is not accepting Batch of events (more than 1), as HTTP is not transactional. I was not sure on how to handle this properly without breaking the transaction behavior of Flume Channels. Therefore i did not work on that, even if that could improve performances even more.

Any comment is welcome: i will submit for review!

> Adding an HTTP Sink
> -------------------
>
>                 Key: FLUME-2524
>                 URL: https://issues.apache.org/jira/browse/FLUME-2524
>             Project: Flume
>          Issue Type: New Feature
>          Components: Sinks+Sources
>    Affects Versions: v1.6.0
>            Reporter: Jeff Guilmard
>             Fix For: v1.6.0
>
>         Attachments: FLUME-2524-0.patch, FLUME-2524-1.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Flume whould have an HTTP Sink, with following capacities:
> - Using up to date performant Http Client
> - Capacity to load balance on multiple target servers (simple round robin)
> - Handle HTTP Authentication
> - use HTTP POST
> - Capacity to send binary data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)