[jira] [Updated] (HUDI-6394) Fixed the issue that CreateHoodieTableCommand does not provide detailed exception stack trace

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HUDI-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated HUDI-6394:
---------------------------------
    Labels: pull-request-available  (was: )

> Fixed the issue that CreateHoodieTableCommand does not provide detailed exception stack trace
> ---------------------------------------------------------------------------------------------
>
>                 Key: HUDI-6394
>                 URL: https://issues.apache.org/jira/browse/HUDI-6394
>             Project: Apache Hudi
>          Issue Type: Bug
>          Components: spark
>            Reporter: Yao Zhang
>            Assignee: Yao Zhang
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 0.14.0
>
>
> If we encountered an exception when creating table using Hudi with Spark. The log would only show the exception class name and its message. For ClassNotFoundException it might be enough to trace the root cause. 
> However, for other types of exceptions, their messages might not clear enough to demonstrate where the underlying problems locate. I think we should long the detailed stack trace. Another benefit is, the typical pattern of the stack trace in log file could help people or even automatical shell script to capture the exception.
> If it is necessary to add the stack trace in log file, I would like to do it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)