-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.lang.IllegalArgumentException: requirement failed while read migrated parquet table #8863
Comments
I'm lost.... seems both snapshot and migrate use and I try to:
|
I've just encountered this exception as well but the circumstances are somewhat different. One process is writing out an iceberg table primarily via appends with the occasional delete. Upon completion a new cluster is spun up that reads that table. This issue presented itself during that process:
Iceberg 1.4.0, Spark 3.4.1 (EMR 6.14.0), JDK 17. |
after 1.4.2, no IllegalArgumentException |
Upgrading to 1.4.1 or later AND rewriting manifests seems to resolve this. |
Any idea how to overcome this issue if upgrading is not an option? |
This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible. |
This issue has been closed because it has not received any activity in the last 14 days since being marked as 'stale' |
Apache Iceberg version
1.4.0 (latest release)
Query engine
Spark 3.4.1
Please describe the bug 🐞
We have some irrationally partitioned parquet table, which have 3 level partition and have tons of small files. It looks like
table/log_date=2023-10-16/date=2023-10-17/attr=attr1
.after
call spark_catalog.system.migrate("db.table")
success, spark read failed on some of partitions that have about 1k+ parquet(zstd) files (about 30KiB per file), but we can read fromtable_backup_
.Error:
The text was updated successfully, but these errors were encountered: