gaborgsomogyi commented on pull request #30366: URL: https://github.com/apache/spark/pull/30366#issuecomment-728810426
Good to hear the bug will be fixed on Hadoop side. > The question remains, would we still want to make the code be resilient to the bad token identifier, as there're existing Hadoop versions which contain the bug? My personal opinion is yes and no. I don't think we should solve all problem what token providers generate especially because the change can be either risky (using `now`) or complex which could bring in new issues (tracking individually). What I would do is writing out an error message what causes the issue not to spend huge amount of time to find it out next time. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
