anshuksi282-ksolves commented on PR #8636: URL: https://github.com/apache/hadoop/pull/8636#issuecomment-5103420242
> If this doesn't fail only, then what are we fixing. I don't think this is something we need Hi @ayushtkn, thanks for taking a look! To clarify, the test does fail in specific scenarios—specifically when hadoop.security.authentication is set to kerberos (as reported in HADOOP-18814). The issue is that when it fails in that environment, the direct cast (RemoteException)e.getCause() throws a ClassCastException. This completely swallows the actual underlying IOException, making it very confusing and difficult to debug what actually went wrong. This PR doesn't change the core test logic; it just adds a minimal defensive check. If an exception occurs, it ensures the real root cause is surfaced instead of hiding it behind a misleading ClassCastException. Since this was a reported pain point in JIRA (and previously validated in #6076 before going stale), I thought it would be a helpful quality-of-life improvement for developers debugging Kerberos setups. Let me know if that makes sense or if you'd still prefer to skip this! -- 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]
