xtdb 2026-08-29

Hi all. In XTDB v1 I'm trying to upgrade the S3 checkpoint store to use the new AWS transfer manager variant, because we seem to have hit a size limit where the old S3 checkpoint store fails to download a full checkpoint. When pointing a xtdb.s3.checkpoint-transfer-manager store at an S3 bucket containing checkpoints created by the old xtdb.s3.checkpoint store, there seems to be some odd behavior caused by the checkpoint metadata having the key :xtdb.s3.checkpoint/s3-dir instead of :xtdb.s3.checkpoint-transfer-manager/s3-dir. It seems to try and download the entire S3 bucket instead of just the latest checkpoint, which is then not recognized as RocksDB data. From what I can tell it should be safe to modify the metadata file on the latest checkpoint to include s3-dir under both namespaces, but I wanted to check here first just in case that's not true! Appreciate any advice, cheers

Hey @jmerrifield - I'm AFK at the moment but that sounds reasonable, yep 👍

👍 1

All seemed to work fine! Thanks!

🙏 1