-
Notifications
You must be signed in to change notification settings - Fork 218
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
Test out Iceberg 1.7.2 RC0 #1581
base: main
Are you sure you want to change the base?
Conversation
Bumps [pyspark](https://github.com/apache/spark) from 3.5.3 to 3.5.4. - [Commits](apache/spark@v3.5.3...v3.5.4) --- updated-dependencies: - dependency-name: pyspark dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Doesn't look good:
It works on my local machine 🫠 |
0031101
to
f3f6295
Compare
Not to muddy the waters since this probably is not literally the same thing but: I experienced something similar(ish) to this using Iceberg 1.7.1 with Spark 3.5.4. Downgrading to 3.5.3 fixed it, didn't have time to figure out what was actually going on. (I only saw the problem when going MERGE INTOs against tables stored in GCP and only for certain files; integration tests against Minio never surfaced anything like it). Here's what I got:
In my case, I do have a setup where I am co-mingling edits to table metadata (schema updates) made by pyiceberg with writes made by Spark/pyspark, so I do think the interplay may be related somehow. I never got this failure on initial table write, only when subsequently upserting to a table that some data in it. |
Thanks @corleyma for jumping in here, at least I'm not alone 😃 You made me think, and I don't think we need to bump Spark separately, as in #1461. Spark 3.5.4 is not yet supported, see apache/iceberg#11731. So we need to bump to 1.7.2 here as well: iceberg-python/tests/conftest.py Line 2426 in 9850290
|
The vote is out: https://lists.apache.org/thread/qorszog7plh5n549pcbrlsp9mvn3qr3d