Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
Description
The TestFunctions tests revealed that NPE is thrown in some cases. These NPEs could be prevented with a simple null check and a MetaException with a proper error message should be thrown instead.
Example: NPE is thrown in the following test cases
- testCreateFunctionNullFunctionName
- testCreateFunctionNullDatabaseName
- testCreateFunctionNullOwnerType
- testCreateFunctionNullFunctionType
- testGetFunctionNullDatabase
- testDropFunctionNullDatabase
- testDropFunctionNullFunctionName
- testAlterFunctionNullDatabase
- testAlterFunctionNullFunctionName
- testAlterFunctionNullFunction
- testAlterFunctionNullFunctionNameInNew
- testAlterFunctionNullDatabaseNameInNew
- testAlterFunctionNullOwnerTypeInNew
- testAlterFunctionNullFunctionTypeInNew
Also there are some alter function tests where InvalidObjectException is thrown with Embedded MetaStore, but TApplicationException it thrown with Remote MetaStore. The reason is that the InvalidObjectException is not defined for the alter_function method in the thrift interface, so we got the TApplicationException when the InvalidObjectException was thrown. In these cases the InvalidObjectException could be handled on the server side and re-throw it as a MetaException
Attachments
Attachments
Issue Links
- links to