[ 
https://issues.apache.org/jira/browse/FLUME-892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213821#comment-13213821
 ] 

[email protected] commented on FLUME-892:
-----------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3831/
-----------------------------------------------------------

(Updated 2012-02-22 18:26:46.629023)


Review request for Flume.


Changes
-------

Re-factored the TCP and UPD sources to use netty package instead of raw socket. 
Also made the sources to event driven.


Summary
-------

syslog source support for Flume 1.x


This addresses bug FLUME-892.
    https://issues.apache.org/jira/browse/FLUME-892


Diffs (updated)
-----

  flume-ng-core/pom.xml d753fa1 
  flume-ng-core/src/main/java/org/apache/flume/source/SyslogTcpSource.java 
PRE-CREATION 
  flume-ng-core/src/main/java/org/apache/flume/source/SyslogUDPSource.java 
PRE-CREATION 
  flume-ng-core/src/main/java/org/apache/flume/source/SyslogUtils.java 
PRE-CREATION 
  flume-ng-core/src/test/java/org/apache/flume/source/TestSyslogUdpSource.java 
PRE-CREATION 

Diff: https://reviews.apache.org/r/3831/diff


Testing
-------

regression tests
Added new test for UDP soruce. tested the TCP source manually. Haven't found a 
package that has the tcp syslog client. will add a testcase with custom tcp 
client to test the source.


Thanks,

Prasad


                
> Support for SysLog as source
> ----------------------------
>
>                 Key: FLUME-892
>                 URL: https://issues.apache.org/jira/browse/FLUME-892
>             Project: Flume
>          Issue Type: New Feature
>          Components: Sinks+Sources
>    Affects Versions: v1.0.0
>            Reporter: Ravi Bulusu
>            Assignee: Prasad Mujumdar
>
> Need SysLog as a source for flume NG.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to