Skip to content

feat: allow result cache - #70

Merged
mrjsj merged 1 commit into
mainfrom
feat/allow-result-cache
Feb 9, 2026
Merged

mrjsj merged 1 commit into
mainfrom
feat/allow-result-cache

Conversation

@mrjsj

@mrjsj mrjsj commented Feb 9, 2026

Copy link
Copy Markdown
Owner

Adds caching mechanism by providing cache_mode to the Blueprint.register() function. It should be either memory or file. If not set, nothing will be cached. If set to memory the dataframe produced by the user-defined transformations will be cached in-memory. If set to file the cache is instead stored as .parquet file in the table_uri destination folder. The cacheefore each run, however it is overwritten on subsequent runs (file cache only).

@mrjsj mrjsj closed this Feb 9, 2026
@mrjsj
mrjsj deleted the feat/allow-result-cache branch February 9, 2026 20:09
@mrjsj
mrjsj restored the feat/allow-result-cache branch February 9, 2026 20:09
@mrjsj mrjsj reopened this Feb 9, 2026
@mrjsj
mrjsj merged commit d02371a into main Feb 9, 2026
6 checks passed
@mrjsj
mrjsj deleted the feat/allow-result-cache branch February 9, 2026 20:09
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.

1 participant