Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-21707

Beeline always exits with fixed code

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Beeline
    • Labels:
      None

      Description

      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, ... ?

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              himanshum Himanshu Mishra
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: