This looks a bit specific and maybe it's better to allow catalogs to
customize the error message, which is more general.
On Wed, May 13, 2020 at 12:16 AM Russell Spitzer
wrote:
> Currently the way some actions work, we receive an error during analysis
> phase. For example, doing a "SELECT *
Currently the way some actions work, we receive an error during analysis
phase. For example, doing a "SELECT * FROM non_existent_table" will return
an analysis exception as the NoSuchTableException is captured and replaced.
Other actions like the "ShowNamespaceExec" call catalog methods directly
