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: make duckdb memory limit configurable via preprocessing config #579

Merged
merged 1 commit into from
Sep 17, 2024

Conversation

Taepper
Copy link
Collaborator

@Taepper Taepper commented Sep 17, 2024

resolves #568

Summary

The memory limit was causing repeated issues as it is handled differently in recent duckdb versions than before. (In theory it is now consistent, but the it only worked smoothly due to inconsistencies in duckdb features that respect the memory limit).

PR Checklist

  • All necessary documentation has been adapted or there is an issue to do so.
  • The implemented feature is covered by an appropriate test.

Copy link
Contributor

github-actions bot commented Sep 17, 2024

This is a preview of the changelog of the next release. If this branch is not up-to-date with the current main branch, the changelog may not be accurate. Rebase your branch on the main branch to get the most accurate changelog.

Note that this might contain changes that are on main, but not yet released.

Changelog:

0.2.20 (2024-09-17)

Features

  • make duckdb memory limit configurable via preprocessing config (a27f501)

@Taepper Taepper merged commit c112eb1 into main Sep 17, 2024
10 checks passed
@Taepper Taepper deleted the duckdb-memory-limit branch September 17, 2024 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Make duckdb memory limit configurable for preprocessing
2 participants