aturoczy commented on PR #4904: URL: https://github.com/apache/hive/pull/4904#issuecomment-1830170710
> NoSuchObjectException This is a dilemma to me. Actually, the NoSuchObjectException does not describe the nature of the exception. It is pretty undescribed, what kind of object. Table, Column, Database etc. An object is missing, but an object could be anything. Which imho is not clear for the API user. On the other hand, the HiveException is too general in the Hive. It wraps everything and does not describe the actual issue till you do not open the details of the exception. Which is also not the best design principals. Of course, it would need a wider agreement. But to me, it will be the following HiveExcption is the root and I would have DatabaseMissingException, TableMissingException, and more detailed exception for those scenarios where the API consumers would read it clearly. cc: @deniskuzZ @ayushtkn @abstractdog -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
