To view this documentation for the Periscope Classic UI, click here.
SQL Views can be materialized on the Periscope Data Cache. This means that the query must be in Redshift-supported syntax. Once a view has been materialized for the first time, it can be used in a query for results almost immediately. It is important to note that Periscope searches for view names prior to table names when building the query.
Note: Materializing Views is only available with the cache add-on.
For a view to materialize the underlying tables must be cached. By default, the Cache Enabled switch is on, and views are materialized automatically. Caching views stores a copy of the view in Periscope, however, if an immediate version of the view is preferred, the switch can be turned off.
After clicking Save, hover over the information dot to check its status.
Materialized views are kept up-to-date in the background to make sure the data is always fresh. Periscope Data refreshes materialized views once every 1-3 hours. Once it's materialized, the info text turns green:
If the info text is yellow, this indicates that the view failed to cache but is going to try again. The query may have timed out or may be waiting on another dependency to be cache. Failing views retry 10 times.
A red info dot indicates that the view failed to materialize.
The "i" next to the View's name display information such as when the View was last refreshed, when the View was last modified, and how many charts and Views depend on this View.
In the list of all Views, the colored dots will give quick summary statuses. Green checks indicate successfully cached Views, no icons indicate Views that are in the process of caching, and red circles indicate cache failures.
In order for a view to successfully materialize, it must follow the same naming conventions described in Redshift's documentation page.