Repository navigation
Commit 1032755
[chore](docker) Re-extract the iceberg fixture when it lacks a mounted jar
### What problem does this PR solve?
Issue Number: None
Related PR: #66346
Problem Summary: Review follow-up. run-thirdparties-docker.sh extracts the
iceberg fixture archive into docker-compose/iceberg/data once and reuses
that directory on later runs. After this PR switches the archive and the
mounted Paimon jars to 1.4.2, an environment that still has the data
directory from the old archive skips the download, the 1.4.2 jars it
mounts do not exist, Compose creates empty directories in their place, and
Spark cannot load the Paimon catalog. CI starts from a clean environment
and is not affected.
start_iceberg now checks every jar iceberg.yaml mounts from
data/input/jars before deciding whether to download. If one is missing (or
is a directory Compose created), the stale data directory is removed and
the current archive is extracted again, the same as a fresh install. Later
jar changes in iceberg.yaml are picked up the same way.
### Release note
None
### Check List (For Author)
- Test: Manual test (bash -n; the new check run on four layouts: all jars
present, a data directory from the old archive, a jar path Compose
created as a directory, and no data directory)
- Behavior changed: No
- Does this need documentation: No
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>1 parent 318fe23 commit 1032755
1 file changed
Lines changed: 13 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1437 | 1437 | | |
1438 | 1438 | | |
1439 | 1439 | | |
| 1440 | + | |
| 1441 | + | |
| 1442 | + | |
| 1443 | + | |
| 1444 | + | |
| 1445 | + | |
| 1446 | + | |
| 1447 | + | |
| 1448 | + | |
| 1449 | + | |
| 1450 | + | |
| 1451 | + | |
| 1452 | + | |
1440 | 1453 | | |
1441 | 1454 | | |
1442 | 1455 | | |
| |||
0 commit comments