[ https://issues.apache.org/jira/browse/FLUME-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840091#comment-15840091 ]
Hari Shreedharan commented on FLUME-3049: ----------------------------------------- I think that is a bug and was an oversight when I reviewed it. I think we should throw the actual exception itself. Please go ahead and throw the actual exception and removing the {{SecurityException}} > Wrapping the exception into SecurityException in UGIExecutor.execute hides > the original one > ------------------------------------------------------------------------------------------- > > Key: FLUME-3049 > URL: https://issues.apache.org/jira/browse/FLUME-3049 > Project: Flume > Issue Type: Bug > Reporter: Denes Arvay > > see: > https://github.com/apache/flume/blob/trunk/flume-ng-auth/src/main/java/org/apache/flume/auth/UGIExecutor.java#L49 > This has unexpected side effects as the callers try to catch the wrapped > exception, for example in {{BucketWriter.append()}}: > https://github.com/apache/flume/blob/trunk/flume-ng-sinks/flume-hdfs-sink/src/main/java/org/apache/flume/sink/hdfs/BucketWriter.java#L563 > I don't know the original intend behind this wrapping, [~jrufus] or > [~hshreedharan], do you happen to remember? (You were involved in the > original implementation in FLUME-2631) > Right now I don't see any problem in removing this and letting the original > exception to propagate as the {{org.apache.flume.auth.SecurityException}} > doesn't appear anywhere in the public interface. -- This message was sent by Atlassian JIRA (v6.3.4#6332)