-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Adding postgres cache support for node #1648
base: main
Are you sure you want to change the base?
Conversation
b735944
to
aae7e9e
Compare
aae7e9e
to
e52aca9
Compare
c1cd90f
to
23e85e8
Compare
23e85e8
to
cacf54f
Compare
@nfcampos looks like |
this should be fixed now -- merged the PR fixing the snapshots |
Summary:
We currently have writes result stored to the mapping data storage. however, during each different execution, we still rerun the execution to get the writes result.
To solve this issue, we provided a CachePolicy which allows people pass in a cache_key which specify how they want to cache this node. It can based up the step name or user id etc.
This version currently only support postgres sync request, but in the future we would like to expand this to support all the data storages and async.
Test:
Added test_cache file.