Github user mridulm commented on the issue: https://github.com/apache/spark/pull/15422 @zsxwing You are right, NewHadoopRDD is not handling this case. Probably would be good to add exception handling there when nextKeyValue throws exception ? Context is, for large jobs/data, it is not unexpected to see some data corruption at times. We dont want to throw out the entire job due to a few bad records. For example, in MR you have the ability to even set the percentage of bad records you want to tolerate (we dont have that in spark).
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org