You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2022/01/14 04:38:20 UTC

[GitHub] [superset] zhaoyongjie edited a comment on pull request #17882: feat: Adds a key-value endpoint to store charts form data

zhaoyongjie edited a comment on pull request #17882:
URL: https://github.com/apache/superset/pull/17882#issuecomment-1011038742


   > > I can create the same cache of form_data and not any limitation. Is it by design?
   > 
   > @zhaoyongjie Yes. It's by design. This is especially useful when a user shares a URL with someone. We save the same content over a different key so that any modification made by a user does not affect the other one.
   
   The problem is that the same user session and the same query payload. It will generate the different cache keys. In the other word, **EVERY** HTTP request will generate a new **record** or **entity** in cache system. It will quickly consume the cache system.
   
   ---------
   Additional information:
   Every POST HTTP request with the same cache entity will generate a new **record** in cache system.
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org