-
Notifications
You must be signed in to change notification settings - Fork 8
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
caching of calculated properties #30
Comments
The The elastic search caching is implemented as To avoid any caching use |
According to @lrowe , calculated properties should be cached and not re-calculated, but @j1z0 with 4dn has reported that they are always calculated.
Let's start by writing a test in snovault to prove this behavior. There are multiple caching mechanisms, but the one that matters is elasticsearch.
It might make sense to actually have calculated properties NOT be indexed in elasticsearch as long as GET/calculate is efficient enough; this could allow us to connect to linked objects that are never embedded and hence will not invalidate the parent object on update.
The text was updated successfully, but these errors were encountered: