You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org> on 2012/04/10 00:01:21 UTC

[jira] [Commented] (FLUME-1114) Syslog Sources does not implement maxsize

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

jiraposter@reviews.apache.org commented on FLUME-1114:
------------------------------------------------------


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

Review request for Flume.


Summary
-------

Implement configurability for maximum event size for SyslogTCPsource and maximum size for Udp source as per RFC


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


Diffs
-----

  flume-ng-core/src/main/java/org/apache/flume/source/SyslogTcpSource.java c5964ae 
  flume-ng-core/src/main/java/org/apache/flume/source/SyslogUDPSource.java eb483da 
  flume-ng-core/src/main/java/org/apache/flume/source/SyslogUtils.java 061ec95 

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


Testing
-------

All current unit tests pass


Thanks,

Hari


                
> Syslog Sources does not implement maxsize 
> ------------------------------------------
>
>                 Key: FLUME-1114
>                 URL: https://issues.apache.org/jira/browse/FLUME-1114
>             Project: Flume
>          Issue Type: Bug
>          Components: Sinks+Sources
>    Affects Versions: v1.1.0
>            Reporter: Hari Shreedharan
>            Assignee: Hari Shreedharan
>
> Even though a variable "maxsize" is declared in UDP source, but is unused. In tcp source, maximum event size should be configurable.

--
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