Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15983
@gatorsmile I think this behavior change is necessary for the new "Scalable
Partition Handling" feature. BTW, the table created by Spark 2.0 can still be
read by Spark 2.1 without `REPAIR TABLE`, and users can fall back to the old
behavior by turn off `spark.sql.hive.manageFilesourcePartitions`. So the
backward compatibility is still good.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
