Create View Component

Create View Component

The "Create View" component allows you to output a view definition to the Redshift cluster. In some circumstances, that may be preferable to writing the data to a physical table.

The "Create View" component allows you to output a view definition to the Snowflake warehouse. In some circumstances, that may be preferable to writing the data to a physical table.

The "Create View" component allows you to output a view definition to the Big Query Project. In some In some circumstances, that may be preferable to writing the data to a physical table.

If an existing view with the same name exists, it will be replaced. If an existing table with the same name exists, then the step will fail - it will not replace an existing table, only a view.

The views created by this component are somewhat isolated from the other views created as part of normal operation. It will NOT be dropped when the job is re-validated, but will get recreated at runtime when the job is executed.

Note:This component cannot create views using external schemas.

Properties

Property Setting Description
Name Text The descriptive name for the component.
Database Select The name of the database that the new view belongs to.
Project Text The name of the Google Cloud Project the source table exists on.
Dataset Select Select the table dataset. The special value, [Environment Default] will use the dataset defined in the environment.
For more information on Google Cloud Datasets, visit the official documentation.
Schema Select Select the table schema. The special value, [Environment Default] will use the schema defined in the environment. For more information on using multiple schemas, see this article.
View Name Text Any valid view name.
Late binding Select If set to 'Yes', creates a late-binding view. Late-binding views do not check referenced tables until queried. As such, late-binding views can reference external tables and are not automatically dropped when the underlying table is dropped.

Strategy

Generates a permanent, named-view, containing the SQL generated by all the input tables up to the Create View component.

Example

This example creates a view over the Accounts table, applying a filter to select New Accounts.

Only the View Name needs to be completed:

Whenever "new_accounts_view" is read, it will reflect the current contents of the Accounts table with the filter applied.