Vortex spark integration is a fileformat not a tableprovider

[robert3005]

Following in the footsteps of duckdb integration we now claim to be a fileformat
instead of tableprovider thus better aligning with existing functionality

We also add shared java io layer that can you JvmWrite/JvmReadAt

Signed-off-by: Robert Kruszewski github@robertk.io

[codspeed]

Merging this PR will degrade performance by 11.56%

⚠️ 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.

⚠️ 12 benchmarks spent significant time in system calls

System calls cannot be consistently instrumented, so they are not included in the measure, which understates the real cost. Please switch to the Walltime instrument to accurately measure system calls.

Measurement and system calls

• compress_fsst[(500, 16, 8)]
• random_i128[0.01]
• optimize_lookup_predicate[ids=256, shape=in_list]
• from_vec_drop_vortex[65536]
• filter_run_end[len=4096_run=16_density=0.1]
• multipolygon_mixed_validity
• take_varbin
• ilike_contains
• zstd_compress_string
• decompress[u32, (1000, 256)]
• …and 2 more

⚠️ 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

❌ 1 regressed benchmark
✅ 2182 untouched benchmarks
⏩ 359 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	WallTime	bitpack_blocked_compress_avx2	6.8 µs	7.6 µs	-11.56%

Tip

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

---

_{Comparing rk/sparkfileformat (4c1310f) with develop (3d12093)}

Footnotes

1. 359 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. ↩

[github-actions]

This PR has been marked as stale because it has been open for 14 days with no activity. Please comment or remove the stale label if you wish to keep it active, otherwise it will be closed in 7 days

[github-actions]

This PR was closed because it has been inactive for 7 days since being marked as stale.