[GitHub] [druid] abhishekagarwal87 commented on issue #13123: Enhanced Druid Exceptions for improved user error messages

[GitBox <gi...@apache.org>]

abhishekagarwal87 commented on issue #13123:
URL: https://github.com/apache/druid/issues/13123#issuecomment-1256935943

   Thanks for writing this up. We also would like to be able to store these exceptions in the database. We do that already for task failures message for example but there is a limit to the size of error text. With that in mind, I am thinking that we have an error code and a verbose error message associated with that example. And we only need to store the error code in the database but not the verbose error message. 
   
   For example, a task failed because there were no valid input records. Now, that can be caused by a bad timestamp spec, a badly configured filter, or because data has multiple values for some column in each row. We don't want to put all these reasons in the database when storing task result status. I can store `NO_VALID_INPUT_RECORDS` as the error code and then map it to a nice error message in the application. What do you think? 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org