Pre-release, same channel as 11.0.368.
Writer and compaction no longer send X-Amz-Security-Token when static S3 keys are configured. That header is what Vultr Object Storage (Ceph RGW) answered with HTTP 400 (#1086, #1088). Until this image is pulled, unsetting AWS_SESSION_TOKEN in the pod is the workaround.
The external file cache now stays off on the writer, compaction and tiering instances, including remote lakes, so compaction of small parquet files does not grow RSS without a plateau (#1074, #1089). The node still keeps the cache for remote search hits. tuning.external_file_cache forces it either way.
What's Changed
- fix(storage): drop ambient AWS session token on static S3 keys by @adubovikov in #1088
- fix(security): bind tiered table lookup parameters by @adubovikov in #1087
- fix(storage): disable DuckDB's external file cache on the lake instances by @hoilchoi in #1074
- fix(storage): keep the external file cache off on write-path DuckDB by @adubovikov in #1089
Full Changelog: 11.0.368...11.0.369