Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16083
Can one of the admins verify this patch?
---
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 feat
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16083
Actually, I don't know (or heard of) how the schema is corrupt. I guess any
committer should verify this before merging it. How about asking this to
dev/user mailing list if you are not sure? If
Github user jayadevanmurali commented on the issue:
https://github.com/apache/spark/pull/16083
Hi @HyukjinKwon ,
I tried to corrupt the metadata by editing files under spark/warehouse
directory. But it is not working. Do you have any idea to corrupt metadata
manually.
Thanks
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16083
Hi @jayadevanmurali, are you still working on this? It seems inactive for
few months. Maybe, it might better be closed for now if you are currently not
able to proceed further.
---
If your pro
Github user thomastechs commented on the issue:
https://github.com/apache/spark/pull/16083
This patch would be catching the exception happening while the
metadatacheck(due to getting corrupted) and continue with a warning log and
continue with the drop operation...
---
If your proje
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16083
Can one of the admins verify this patch?
---
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 feat
