docs(vortex-layout): mark the bloom filter aggregate as unstable

[connortsui20]

Summary

• Tracking Issue: Tracking Issue: Skipping Indexes on ZonedLayout #8901

The bloom filter aggregate from #9398 does not have a settled wire format. The hash function, the block layout, and the salt order can all still change, and no edition declares vortex.bloom_filter.sbbf, so nothing must write bloom partials into a file yet.

Changes

Adds a Stability section to the BloomFilter doc comment saying that the aggregate is unstable and that vortex.bloom_filter.sbbf partials must not be persisted. Comment only, no behavior change.

[codspeed-hq]

Merging this PR will regress 2 benchmarks

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

⚡ 2 improved benchmarks
❌ 2 regressed benchmarks
✅ 2195 untouched benchmarks
⏩ 206 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	random_i8[0.5]	67 µs	90.6 µs	-26.02%
❌	Simulation	allocate_drop_bytes[0]	466 ns	520.2 ns	-10.41%
⚡	WallTime	arrow_checked_add_u32_neon[16384]	20.4 µs	12.7 µs	+60.18%
⚡	Simulation	random_i16[0.8]	92.7 µs	74.3 µs	+24.76%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing claude/aggregate-fn-unstable-comment-j95028 (6dd8679) with develop (3170657)}

Footnotes

1. 206 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[robert3005]

Things not in editions cannot be persisted anyway. The editions are the reference of what’s persistable. Happy with the docs fwiw just letting you know there’s layers to safety now