Ability to separately change the caching period for each Live model

[zebben]

At the moment, the caching period of live models is set for the whole instance which removed flexibility where you'd want the caching period to be different for exceptionally large models.  For example, we have a table we have to ingest via a live connection as it is too big for elasticubes - but wouldn't want the caching period for this live connection to be too "low" as it would cost a lot via AWS.  However, we would want a low caching period for low latency reporting

[DRay]

Hi @zebben.

Thank you for your feedback! I would like to get this Idea over to the product team, but first I would like to get more information and head off any roadblocks to implementation.

For your use case, could you use an Elasticube for that specific Table, and a Live Connection for the rest? https://docs.sisense.com/main/SisenseLinux/creating-a-dashboard-with-multiple-sources.htm

Thank you for working with me to get this Idea fleshed out so it can be evaluated and scoped for effort.

Have a great day!