Configurable and triggerable caching for cross-cloud and inter-region queries in OneLake

In the Fabric launch, it was mentioned that cross-cloud and inter-region queries in OneLake would utilize smart caching to optimize on egress charges and performance of these distributed queries.

It will be very useful to be able to trigger cache invalidations and refreshes for this technology. An opaque cache layer that is attempting to be smart is a path to pain for someone's use case, and my luck tells me it is likely my own use case.

Many data processes are still batch oriented, and many modern processes are event driven. Both of these are better supported by a triggerable cache refresh than by any smart heuristic.

Please do not make more opaque and hard to manage features. A smart layer is great, only insofar as we can troubleshoot and override it when necessary.