createMaterializedView - Kinetica Docs

◆ createMaterializedView() [1/4]

CreateMaterializedViewResponse gpudb::GPUdb::createMaterializedView ( const CreateMaterializedViewRequest & request_ ) const

Initiates the process of creating a materialized view, reserving the view’s name to prevent other views or tables from being created with that name.

For materialized view details and examples, see Materialized Views.

The response contains viewId, which is used to tag each subsequent operation (projection, union, aggregation, filter, or join) that will compose the view.

Parameters

[in] request_ Request object containing the parameters for the operation.

Returns

Response object containing the result of the operation.

◆ createMaterializedView() [2/4]

CreateMaterializedViewResponse & gpudb::GPUdb::createMaterializedView	(	const CreateMaterializedViewRequest &	request_,
		CreateMaterializedViewResponse &	response_ ) const

Initiates the process of creating a materialized view, reserving the view’s name to prevent other views or tables from being created with that name.

For materialized view details and examples, see Materialized Views.

The response contains viewId, which is used to tag each subsequent operation (projection, union, aggregation, filter, or join) that will compose the view.

Parameters

[in]	request_	Request object containing the parameters for the operation.
[out]	response_	Response object containing the results of the operation.

Returns

Response object containing the result of the operation (initially passed in by reference).

◆ createMaterializedView() [3/4]

CreateMaterializedViewResponse gpudb::GPUdb::createMaterializedView	(	const std::string &	tableName,
		const std::map< std::string, std::string > &	options ) const

Initiates the process of creating a materialized view, reserving the view’s name to prevent other views or tables from being created with that name.

For materialized view details and examples, see Materialized Views.

The response contains viewId, which is used to tag each subsequent operation (projection, union, aggregation, filter, or join) that will compose the view.

Parameters

[in]	tableName	Name of the table to be created that is the top-level table of the materialized view, in [schema_name.]table_name format, using standard name resolution rules and meeting table naming criteria.
[in]	options	Optional parameters. create_materialized_view_collection_name: [DEPRECATED–please specify the containing schema for the materialized view as part of tableName and use createSchema to create the schema if non-existent] Name of a schema which is to contain the newly created view. If the schema provided is non-existent, it will be automatically created. create_materialized_view_execute_as: User name to use to run the refresh job. create_materialized_view_build_materialized_view_policy: Sets startup materialized view rebuild scheme. Supported values: create_materialized_view_always: Rebuild as many materialized views as possible before accepting requests. create_materialized_view_lazy: Rebuild the necessary materialized views at start, and load the remainder lazily. create_materialized_view_on_demand: Rebuild materialized views as requests use them. create_materialized_view_system: Rebuild materialized views using the system-configured default. The default value is create_materialized_view_system. create_materialized_view_persist: If true, then the materialized view specified in tableName will be persisted and will not expire unless a ttl is specified. If false, then the materialized view will be an in-memory table and will expire unless a ttl is specified otherwise. Supported values: create_materialized_view_true create_materialized_view_false The default value is create_materialized_view_false. create_materialized_view_enable_mv_input_wrappers: If true, each base table the view reads is accessed through a wrapper view so an in-progress out-of-place update cannot make a record momentarily disappear from the view, and a long refresh does not block updates to the base tables. Overrides the gaia.enable_mv_input_wrappers configuration default when set. Supported values: create_materialized_view_true create_materialized_view_false The default value is create_materialized_view_false. create_materialized_view_refresh_span: Sets the future time-offset(in seconds) at which periodic refresh stops. create_materialized_view_refresh_stop_time: When refresh_method is periodic, specifies the time at which a periodic refresh is stopped. Value is a datetime string with format ‘YYYY-MM-DD HH:MM:SS’. create_materialized_view_refresh_method: Method by which the join can be refreshed when the data in underlying member tables have changed. Supported values: create_materialized_view_manual: Refresh only occurs when manually requested by calling alterTable with an ‘action’ of ‘refresh’. create_materialized_view_on_query: Refresh any time the view is queried. create_materialized_view_on_change: If possible, incrementally refresh (refresh just those records added) whenever an insert, update, delete or refresh of input table is done. A full refresh is done if an incremental refresh is not possible. create_materialized_view_periodic: Refresh table periodically at rate specified by refresh_period. The default value is create_materialized_view_manual. create_materialized_view_refresh_period: When refresh_method is periodic, specifies the period in seconds at which refresh occurs. create_materialized_view_refresh_start_time: When refresh_method is periodic, specifies the first time at which a refresh is to be done. Value is a datetime string with format ‘YYYY-MM-DD HH:MM:SS’. create_materialized_view_ttl: Sets the TTL of the table specified in tableName. The default value is an empty map.

Returns

Response object containing the result of the operation.

◆ createMaterializedView() [4/4]

CreateMaterializedViewResponse & gpudb::GPUdb::createMaterializedView	(	const std::string &	tableName,
		const std::map< std::string, std::string > &	options,
		CreateMaterializedViewResponse &	response_ ) const

Initiates the process of creating a materialized view, reserving the view’s name to prevent other views or tables from being created with that name.

For materialized view details and examples, see Materialized Views.

The response contains viewId, which is used to tag each subsequent operation (projection, union, aggregation, filter, or join) that will compose the view.

Parameters

[in]	tableName	Name of the table to be created that is the top-level table of the materialized view, in [schema_name.]table_name format, using standard name resolution rules and meeting table naming criteria.
[in]	options	Optional parameters. create_materialized_view_collection_name: [DEPRECATED–please specify the containing schema for the materialized view as part of tableName and use createSchema to create the schema if non-existent] Name of a schema which is to contain the newly created view. If the schema provided is non-existent, it will be automatically created. create_materialized_view_execute_as: User name to use to run the refresh job. create_materialized_view_build_materialized_view_policy: Sets startup materialized view rebuild scheme. Supported values: create_materialized_view_always: Rebuild as many materialized views as possible before accepting requests. create_materialized_view_lazy: Rebuild the necessary materialized views at start, and load the remainder lazily. create_materialized_view_on_demand: Rebuild materialized views as requests use them. create_materialized_view_system: Rebuild materialized views using the system-configured default. The default value is create_materialized_view_system. create_materialized_view_persist: If true, then the materialized view specified in tableName will be persisted and will not expire unless a ttl is specified. If false, then the materialized view will be an in-memory table and will expire unless a ttl is specified otherwise. Supported values: create_materialized_view_true create_materialized_view_false The default value is create_materialized_view_false. create_materialized_view_enable_mv_input_wrappers: If true, each base table the view reads is accessed through a wrapper view so an in-progress out-of-place update cannot make a record momentarily disappear from the view, and a long refresh does not block updates to the base tables. Overrides the gaia.enable_mv_input_wrappers configuration default when set. Supported values: create_materialized_view_true create_materialized_view_false The default value is create_materialized_view_false. create_materialized_view_refresh_span: Sets the future time-offset(in seconds) at which periodic refresh stops. create_materialized_view_refresh_stop_time: When refresh_method is periodic, specifies the time at which a periodic refresh is stopped. Value is a datetime string with format ‘YYYY-MM-DD HH:MM:SS’. create_materialized_view_refresh_method: Method by which the join can be refreshed when the data in underlying member tables have changed. Supported values: create_materialized_view_manual: Refresh only occurs when manually requested by calling alterTable with an ‘action’ of ‘refresh’. create_materialized_view_on_query: Refresh any time the view is queried. create_materialized_view_on_change: If possible, incrementally refresh (refresh just those records added) whenever an insert, update, delete or refresh of input table is done. A full refresh is done if an incremental refresh is not possible. create_materialized_view_periodic: Refresh table periodically at rate specified by refresh_period. The default value is create_materialized_view_manual. create_materialized_view_refresh_period: When refresh_method is periodic, specifies the period in seconds at which refresh occurs. create_materialized_view_refresh_start_time: When refresh_method is periodic, specifies the first time at which a refresh is to be done. Value is a datetime string with format ‘YYYY-MM-DD HH:MM:SS’. create_materialized_view_ttl: Sets the TTL of the table specified in tableName. The default value is an empty map.
[out]	response_	Response object containing the results of the operation.

Returns

Response object containing the result of the operation (initially passed in by reference).

​◆ createMaterializedView() [1/4]

​◆ createMaterializedView() [2/4]

​◆ createMaterializedView() [3/4]

​◆ createMaterializedView() [4/4]

◆ createMaterializedView() [1/4]

◆ createMaterializedView() [2/4]

◆ createMaterializedView() [3/4]

◆ createMaterializedView() [4/4]