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

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


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


Thanks for the patch Mike. The changes look good. Some suggestions follow:

1. Please use 80 char limit on line lengths and wrap the lines where necessary. 
Also the general formatting/style convention is that we should use spaces only, 
two-spaces per tab and no trailing whitespaces in the sources. Any trailing 
whitespaces are highlighted with red in the reviewboard.

2. An event builder in the  org.apache.flume package that can be used to create 
events with a single string or object will be a great complementing addition.

3. Now that the simple to use client API is there, we should refactor the 
AvroCLIClient and Log4jAppender to use it instead of directly going via the 
low-level API.


flume-ng-sdk/src/main/java/org/apache/flume/api/client/AvroClientBuilder.java
<https://reviews.apache.org/r/4047/#comment11668>

    Adding a check on batch size should be good too.


- Arvind


On 2012-02-24 22:47:13, Mike Percy wrote:
bq.  
bq.  -----------------------------------------------------------
bq.  This is an automatically generated e-mail. To reply, visit:
bq.  https://reviews.apache.org/r/4047/
bq.  -----------------------------------------------------------
bq.  
bq.  (Updated 2012-02-24 22:47:13)
bq.  
bq.  
bq.  Review request for Flume.
bq.  
bq.  
bq.  Summary
bq.  -------
bq.  
bq.  Seeking early feedback on some additional APIs to make integrating with 
Flume 1.x easier.
bq.  
bq.  Added the following APIs:
bq.   - AvroClient: Friendly Java interface around the Avro API
bq.   - AvroClientBuilder: Builder class to allow easy extension of AvroClient 
capabilities in the future (i.e. SSL)
bq.   - DefaultAvroClient: Implementation of the AvroClient interface
bq.  
bq.  Created this stuff in a flume-ng-sdk Maven submodule and moved the Event 
interface to that submodule. flume-ng-core depends on flume-ng-sdk.
bq.  
bq.  I also modified AvroSink to use the AvroClient API instead of the bare 
AvroSourceProtocol API directly.
bq.  
bq.  
bq.  This addresses bug FLUME-989.
bq.      https://issues.apache.org/jira/browse/FLUME-989
bq.  
bq.  
bq.  Diffs
bq.  -----
bq.  
bq.    flume-ng-core/pom.xml d753fa1 
bq.    flume-ng-core/src/main/avro/flume.avdl 40da3ef 
bq.    flume-ng-core/src/main/java/org/apache/flume/Event.java a017705 
bq.    flume-ng-core/src/main/java/org/apache/flume/sink/AvroSink.java 5440631 
bq.    flume-ng-sdk/pom.xml PRE-CREATION 
bq.    flume-ng-sdk/src/main/avro/flume.avdl PRE-CREATION 
bq.    flume-ng-sdk/src/main/java/org/apache/flume/Event.java PRE-CREATION 
bq.    flume-ng-sdk/src/main/java/org/apache/flume/api/client/AvroClient.java 
PRE-CREATION 
bq.    
flume-ng-sdk/src/main/java/org/apache/flume/api/client/AvroClientBuilder.java 
PRE-CREATION 
bq.    
flume-ng-sdk/src/main/java/org/apache/flume/api/client/DefaultAvroClient.java 
PRE-CREATION 
bq.    pom.xml d785762 
bq.  
bq.  Diff: https://reviews.apache.org/r/4047/diff
bq.  
bq.  
bq.  Testing
bq.  -------
bq.  
bq.  
bq.  Thanks,
bq.  
bq.  Mike
bq.  
bq.


                
> Factor Flume Avro RPC interfaces out into separate Client SDK
> -------------------------------------------------------------
>
>                 Key: FLUME-989
>                 URL: https://issues.apache.org/jira/browse/FLUME-989
>             Project: Flume
>          Issue Type: Sub-task
>    Affects Versions: v1.0.0
>            Reporter: Mike Percy
>            Assignee: Mike Percy
>             Fix For: v1.1.0
>
>
> Factor out the network RPC APIs so that there is a concise API boundary 
> between user and developer APIs.

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