You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem?
Currently, in case spark throws exception such as AnalysisException, it is handled by processQueryException to generate right error message for the error thrown.
If statementExecutionManager doesn't collect data from the Dataframe, the error is raised from dataToWrite.foreach in finally block, and the error won't be processed correctly and all the errors are reported as Failed to write to result index. ....
FlintREPL doesn't have this problem, since it calls queryResultWriter.processDataFrame within the try block, and raise error from there.
What solution would you like?
Make it throw the exceptions from the try block, or process the exceptions thrown from dataToWrite.foreach.
What alternatives have you considered?
n/a
Do you have any additional context?
The text was updated successfully, but these errors were encountered:
ykmr1224
changed the title
[FEATURE] Improve error message when Catalyst raised AnalysisException
[FEATURE] Improve error message when error is raised from dataToWrite.foreach in JobOperator
Dec 5, 2024
Is your feature request related to a problem?
Currently, in case spark throws exception such as AnalysisException, it is handled by processQueryException to generate right error message for the error thrown.
If statementExecutionManager doesn't collect data from the Dataframe, the error is raised from
dataToWrite.foreach
infinally
block, and the error won't be processed correctly and all the errors are reported asFailed to write to result index. ...
.FlintREPL doesn't have this problem, since it calls
queryResultWriter.processDataFrame
within the try block, and raise error from there.What solution would you like?
Make it throw the exceptions from the
try
block, or process the exceptions thrown fromdataToWrite.foreach
.What alternatives have you considered?
n/a
Do you have any additional context?
The text was updated successfully, but these errors were encountered: