ingestr v1.1.63 - Iceberg Merge and S3 Tables Fixes

ingestr v1.1.63 was published on October 6, 2026. The headline is Iceberg support for AWS S3 Tables: an iceberg-go bump for S3 Tables through Glue, plus fixes for Iceberg merge and SigV4 signing. It is a stable release, not a prerelease.

The full release notes and downloads are on the GitHub release page.

The release has two changes, both from the same contributor, and both target the same destination path. That makes it easy to summarize. It also means the notes say little about internals, so this post sticks to what they state.

The first change is PR 1275, titled “Bump iceberg-go for S3 Tables via Glue”. The release notes give no more detail than the title.

Read plainly, ingestr depends on iceberg-go for its Iceberg writes, and the dependency moved to a version that can reach S3 Tables through the Glue catalog path. If you run ingestr against an S3 Tables bucket and the Glue route was failing or unsupported on the previous pin, this is the change that addresses it.

Two caveats. The notes do not list the iceberg-go version it moved to. They also do not say which ingestr releases failed against S3 Tables. Check the pull request diff if you need the exact version for a dependency audit.

The second change is PR 1281, “Fix Iceberg merge and SigV4 for S3 Tables”. It bundles two separate problems.

The first is the merge path. Merge is the incremental strategy that matters for most production pipelines, because append only loads duplicate rows on retries. A bug in Iceberg merge usually shows up as wrong row counts or a failed run, not as a clean error at startup. If you use merge against Iceberg destinations, compare row counts after the upgrade on a table you can afford to reload.

The second is SigV4 request signing for S3 Tables. S3 Tables requests go through AWS signing, and a signing mismatch typically surfaces as an authorization failure from the service even when IAM permissions look correct. The notes do not describe the exact mismatch. They only say it was fixed.

If your runs failed with 403 style errors against S3 Tables while the same credentials worked elsewhere, this release is the one to try.

There are no new sources, no CLI flag changes, and no config key changes in the notes. The only other item is the changelog link, which compares v1.1.62…v1.1.63. Reading that diff is the fastest way to confirm the scope.

If you do not write to Iceberg on S3 Tables, there is no stated reason to hurry. Other destinations are not mentioned in the notes.

The notes list no breaking changes or migration steps. Because the dependency bump touches the Iceberg write path, a sensible rollout is:

  • Run a staging load into an S3 Tables namespace first.
  • Test one merge strategy table with known duplicate keys.
  • Confirm the IAM role used for signing can reach the Glue catalog and the table bucket.
  • Pin the previous tag if row counts differ, and open an issue with the table schema.

The last two steps are operator advice, not statements from the release notes.