This repository was archived by the owner on Jul 21, 2025. It is now read-only.
feat: duckdb extensions in lambda #75
Merged
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.
@ceholden I took your good work in #60 and reshaped it a bit to use the targeted extension fetching from stac-utils/rustac-py#81. Lambda sizes:
Things are broken, because I haven't wired up the server to actually use those extensions, but I think this is a proof out of using pre-fetched DuckDB extensions. Lambda is here: https://us-west-2.console.aws.amazon.com/lambda/home?region=us-west-2#/functions/stac-fastapi-geoparquet-labs-375-de-lambda8B5974B5-W1CWbXEHRA1Y?tab=code
Warning
When I tried to use the wheels directly, the size got too big. For now, I'm sticking with a build-in-the-container (which is slow, ~10 minutes on my machine), but I need to dig in to why the build is smaller than the wheel.