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

Hudson commented on FLUME-1713:
-------------------------------

Integrated in flume-trunk #333 (See 
[https://builds.apache.org/job/flume-trunk/333/])
    FLUME-1713. Netcat source should allow for *not* returning "OK" upon 
receipt of each message. (Revision e257e3db054d8a8282bfb14187f2dadf8e3c13e4)

     Result = UNSTABLE
mpercy : 
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=e257e3db054d8a8282bfb14187f2dadf8e3c13e4
Files : 
* flume-ng-core/src/main/java/org/apache/flume/source/NetcatSource.java
* flume-ng-node/src/test/java/org/apache/flume/source/TestNetcatSource.java
* 
flume-ng-core/src/main/java/org/apache/flume/source/NetcatSourceConfigurationConstants.java
* flume-ng-doc/sphinx/FlumeUserGuide.rst

                
> Netcat source should allow for *not* returning "OK" upon receipt of each 
> message
> --------------------------------------------------------------------------------
>
>                 Key: FLUME-1713
>                 URL: https://issues.apache.org/jira/browse/FLUME-1713
>             Project: Flume
>          Issue Type: Improvement
>          Components: Easy
>    Affects Versions: v1.2.0
>            Reporter: Mike Percy
>            Assignee: Rahul Ravindran
>            Priority: Minor
>              Labels: newbie
>             Fix For: v1.3.0
>
>         Attachments: 
> 0001-FLUME-1713-Netcat-source-should-allow-for-not-return.patch, 
> final_patch.diff
>
>
> Right now, the Netcat source returns "OK" when each message is processed. In 
> reality, this means that using netcat to send to the "Netcat source" will in 
> most cases not work as expected. It will stall out if the responses are not 
> read back once the TCP receive buffers fill up.
> The default configuration setup should remain the same though.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to