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

Ship it!


+1

Thanks for the patch Mike. Please attach it to the Jira. Also, it will be great 
if you can file a follow-up jira to remove the configuration constants from the 
system into their own separate class.

- Arvind


On 2012-03-22 08:06:39, Mike Percy wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/4360/
> -----------------------------------------------------------
> 
> (Updated 2012-03-22 08:06:39)
> 
> 
> Review request for Flume.
> 
> 
> Summary
> -------
> 
> This is an initial pass at an implementation of HDFS security. I think it 
> will probably work. Currently trying to get Kerberos to play nice with the 
> cluster on my VM though, so I haven't successfully tested it yet. It still 
> works when used on HDFS with security disabled. :)
> 
> The only thing I don't like is in configure() when authentication fails I 
> throw a FlumeException. I'll trace up and see how bad that would be but it 
> seems likely to break something. Just logging the error is kind of a bummer 
> as well, though ... need to ensure process() doesn't fill up the disk while 
> spewing copious error messages into the logs. Maybe this is a use case for 
> some kind of FatalException type thing.
> 
> 
> This addresses bug FLUME-1020.
>     https://issues.apache.org/jira/browse/FLUME-1020
> 
> 
> Diffs
> -----
> 
>   bin/flume-ng 0796a5b 
>   flume-ng-core/src/main/java/org/apache/flume/tools/GetJavaProperty.java 
> PRE-CREATION 
>   flume-ng-sinks/flume-hdfs-sink/pom.xml 1a35baf 
>   
> flume-ng-sinks/flume-hdfs-sink/src/main/java/org/apache/flume/sink/hdfs/HDFSEventSink.java
>  da82f7e 
>   pom.xml 227bca8 
> 
> Diff: https://reviews.apache.org/r/4360/diff
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Mike
> 
>

Reply via email to