First draft for SheetReader extension #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
In the last semester, I was part of a programming project organized by the DIMA group at TU Berlin. We created a small DuckDB-extension named
sheetreader
that utilizes sheetreader-core (a fast multi-threaded XLSX parser) for importing XLSX files into DuckDB.We did a few benchmarks comparing our extension to the import function which the
spatial
extension provides (st_read
). Our first benchmarks indicate, that depending on several factors thesheetreader
extension is around 5 to 10 times faster than thespatial
extension at parsing XLSX files and loading them into DuckDB (https://github.com/polydbms/sheetreader-duckdb/?tab=readme-ov-file#benchmarks).We would like to offer this extension as a DuckDB community extension.
A note regarding the repository structure of our extension:
benchmark-version
that has code dedicated for benchmarking.main
, we provide a “slimmed down” version with that code removed. We would like to offer the latter version as the community extension.