Very similar to lyft_full_load_cached_view_copy. The only difference is that lyft_refresh_view verifies that cache mode is using persistent tables. For in-memory cache mode, it just throws an error. Internally it calls lyft_full_load_cached_view_copy.
Syntax
lyft_refresh_view 'view_name' [;]
Arguments
'view_name'
Fully qualified name of view which cache will be affected.
Example
Refreshes in-memory cache for AdventureWorksDW2012_spark.dbo.DimEmployee.
EXEC lyft_refresh_view 'AdventureWorksDW2012_spark.dbo.DimEmployee';