You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Denes Arvay (JIRA)" <ji...@apache.org> on 2017/01/25 13:55:26 UTC

[jira] [Created] (FLUME-3049) Wrapping the exception into SecurityException in UGIExecutor.execute hides the original one

Denes Arvay created FLUME-3049:
----------------------------------

             Summary: 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)