Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: duckdb server backend #651

Merged
merged 4 commits into from
Feb 24, 2025
Merged

feat: duckdb server backend #651

merged 4 commits into from
Feb 24, 2025

Conversation

gadomski
Copy link
Member

Doesn't quite close #644 b/c here we're just referencing an existing stac-geoparquet file ... going to an in-memory DuckDB database is a different thing.

@gadomski gadomski added [crate] cli stac-cli [crate] server stac-server labels Feb 24, 2025
@gadomski gadomski self-assigned this Feb 24, 2025
@gadomski gadomski changed the title feat: duckdb server feat: duckdb server backend Feb 24, 2025
@gadomski gadomski merged commit 8dada83 into main Feb 24, 2025
11 checks passed
@gadomski gadomski deleted the server/duckdb-backend branch February 24, 2025 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[crate] cli stac-cli [crate] server stac-server
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use DuckDB for in-memory server backend
1 participant