abhishekagarwal87 opened a new pull request, #13815: URL: https://github.com/apache/druid/pull/13815
Recently ran into a situation where a task failed with an error "Aborting Transaction". The error is not user-friendly and doesn't really tell the user what they can do about it. In this PR, I try to surface the actual error that caused the transaction to be aborted. So users don't have to stitch together an error in overlord logs and a failure message in task reports to figure out what's going on. Apart from that, changed the error message of query timeout exceptions. A user, who is issuing a query, doesn't know anything about the sequence iterator. We developers often throw errors that can include too many implementation details. These details can appear daunting to users who are just starting out. This PR has: - [ ] been self-reviewed. - [ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader. - [x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for [code coverage](https://github.com/apache/druid/blob/master/dev/code-review/code-coverage.md) is met. - [ ] been tested in a test Druid cluster. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
