You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For mongodb mode, support for change cache default collection is required, Do not disallow modification of shaker_locks and shaker_cache collections.
Because in actual scenarios, different data may be cached in different collections, which may avoid too much data in a single table.
Decorator api needs to support custom configuration namespace, default file path will cause project migration or function location movement to cause cache invalidation
Hope to support these features as soon as possible.
The text was updated successfully, but these errors were encountered:
Hi, you can setup different namespaces with mongodb in different databases, that should solve having too many keys in the same collection. Just name the databases like cache1_db, cache2_db and so on... You can set the db name in the connection url.
Functions needed and reasons:
Because in actual scenarios, different data may be cached in different collections, which may avoid too much data in a single table.
Hope to support these features as soon as possible.
The text was updated successfully, but these errors were encountered: