Bump to Java Iceberg 1.11.0#3389
Conversation
This reverts commit 03bbbe3.
| retries: 5 | ||
| start_period: 90s | ||
| rest: | ||
| image: apache/iceberg-rest-fixture:1.10.1 |
There was a problem hiding this comment.
we didnt release a new version of iceberg-rest-fixture for 1.11.0 since there was some license issues. will have to fix forward
There was a problem hiding this comment.
I see, thanks for pointing that out. We can also go back to the nightlies. We were blocked by the Spark release 👍
There was a problem hiding this comment.
I'd vote on using nightlies personally. Hopefully, we don't have a full year between releases, but we're merging a lot of PRs in between releases. It'll be nice to get those in the fixture.
There was a problem hiding this comment.
Without the tag it points at the nightly, which I like since we also know when Java makes a breaking chance of some sort. This happens very rarely.
There was a problem hiding this comment.
Had to update this test since REST has some limitations with slashes:
|
@Fokko can you rerun the integration test runner? That's the most important one. |
There is no published `apache/iceberg-rest-fixture:1.11.0` image (Docker Hub only has up to `1.10.1` plus `latest`), and the `1.10.x` images predate the server-side scan-planning support that landed on `main` in late 2025. Use the `latest` tag, a recent `main` build that includes the 1.11.x server-side features, so the integration tests can exercise them (e.g. server-side scan planning, apache#1690). Mirrors apache/iceberg-python#3389, which likewise drops the version pin to pick up the 1.11.x fixture.
3 participants
Rationale for this change
This reverts #3240 and we now should be able to support custom
namespace-seperatorAre these changes tested?
Are there any user-facing changes?