You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Himanshu Mishra (JIRA)" <ji...@apache.org> on 2019/05/08 14:35:00 UTC

[jira] [Created] (HIVE-21707) Beeline always exits with fixed code

Himanshu Mishra created HIVE-21707:
--------------------------------------

             Summary: Beeline always exits with fixed code
                 Key: HIVE-21707
                 URL: https://issues.apache.org/jira/browse/HIVE-21707
             Project: Hive
          Issue Type: Improvement
          Components: Beeline
            Reporter: Himanshu Mishra


Beeline process internally knows when there was a connection error, what type of connection error (i.e. timed out, already open, etc. _Beeline#handleSQLException()_) or error while running query. When running a script via beeline, in case of any error the exit code is always 2.

I wish to handle each error in different way from an external script and needed the Beeline to return different codes when it knows exactly what the error is. Should I return error codes like -10, -11, -12 ?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)