Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14207
The table location is not allowed to change. Right?
With the changes of this PR, if the changes on the data/files (pointed by
the table location) affect the table schema, they need to manually call the
`REFRESH` command. Restarting Spark will not cause the schema changes.
Before this PR, if users restart Spark or the corresponding cache item is
replaced, the table schema could be changed without notice. This could be a
potential issue when the read and write are conducted in parallel. This
undocumented behavior could complicate the Spark applications.
The unexpected changes should be avoided. If the schema is changed and the
table fetching is ready for new schema, users should manually issue `REFRESH`
command.
---
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
