No, there isn't one right now. For realtime cases, the data is changing in realtime, so caching the query result might not make sense.
j
Jonathan Meyer
05/27/2021, 5:18 PM
Yes in the case of realtime table the case would be invalidated very often
In case of offline tables, I guess the best way is to add an external cache at the REST API layer ? And invalidate it whenever new segments are pushed