[
https://issues.apache.org/jira/browse/HIVE-28312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor updated HIVE-28312:
--------------------------------
Description:
Instead of just throwing CommandProcessorException, Driver might save the the
error message for query tracking purposes.
2 ways:
1. wrap every occurrence of throwing CommandProcessorException inside driver
PRO: the logging stays inside of Driver (SQLCommand doesn't need to know about
it)
CONS: looks bad, not future-proof, needs Driver code changes at several places
2. catch in SQLOperation and propagate back to Driver
PRO: it looks better, every exception can be caught in a single place
CON: SQLOperation has to call back to the driver to store the error message
> Save error message on Driver level
> ----------------------------------
>
> Key: HIVE-28312
> URL: https://issues.apache.org/jira/browse/HIVE-28312
> Project: Hive
> Issue Type: Improvement
> Reporter: László Bodor
> Priority: Major
>
> Instead of just throwing CommandProcessorException, Driver might save the the
> error message for query tracking purposes.
> 2 ways:
> 1. wrap every occurrence of throwing CommandProcessorException inside driver
> PRO: the logging stays inside of Driver (SQLCommand doesn't need to know
> about it)
> CONS: looks bad, not future-proof, needs Driver code changes at several places
> 2. catch in SQLOperation and propagate back to Driver
> PRO: it looks better, every exception can be caught in a single place
> CON: SQLOperation has to call back to the driver to store the error message
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
