HeartSaVioR commented on pull request #30366: URL: https://github.com/apache/spark/pull/30366#issuecomment-728469839
FYI, fixing S3 identifier's invalid issue date is tracked via https://issues.apache.org/jira/browse/HADOOP-17379 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? If the answer is yes, we could weigh the options we enumerated. IMHO, `consider the issue date as now` is the simplest one, just not 100% sure it's safe to assume. If the answer is no, we can close this PR and mark the issue as "Won't track here" or likewise. ---------------------------------------------------------------- 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]
