The stored procedure
CREATE_REMOTE_TABLE is one of the components of the feature remote tables. The section
Remote Tables of the Administration Guide explains in detail what remote tables are.
This procedure does the following:
Creates a table in the underlying database of a JDBC data source.
Executes a query in the Virtual DataPort server.
Inserts the result of this query into the table of the database created in step #1.
It creates a base view over the table created in step #1.
To perform steps 1 to 3, this procedure invokes the command
CREATE REMOTE TABLE and then, it creates the base view (step #4).
The procedure DROP_REMOTE_TABLE drops the base views created by this procedure, and the table created by it in the underlying databases.
CREATE_REMOTE_TABLE( remote_table_name : text , replace_remote_table_if_exist : boolean , query : text , datasource_database_name : text , datasource_name : text , datasource_catalog : text , datasource_schema : text , base_view_database_name : text , base_view_name : text , base_view_folder : text , replace_base_view_if_exist: boolean , options : text )
remote_table_name: name of the new table in the underlying database of the JDBC data source. It has to be a valid identifier in the target database.
trueand a table with the same name already exists in the database (in the same schema/catalog), the procedure will drop the table and create it again. The default value is
falseso if the table already exists, the procedure will fail.
query: query executed in the Virtual DataPort server to obtain the data that will be inserted in the new table of the database.
datasource_database_name(optional): database of the JDBC data source in which the new table will be created. If
null, it looks for
datasource_nameon the current database.
datasource_name: JDBC data source that points to the database in which the table will be created.
datasource_catalog: catalog of the database where the table will be created. It is mandatory but if the database does not support catalogs, set this to
datasource_schema: schema of the database where the table will be created. It is mandatory but if the database does not support schemas, set this to
base_view_database_name(optional): Virtual DataPort database where the base view will be created. If
null, the base view is created in the current database.
base_view_name(optional): name of the new base view. If
null, the name will be the value of
base_view_folder(optional): folder in which the base view will be created. If the folder does not exist, the procedure will create it. If
null, the base view will be created in the root folder.
trueand a view with the same name already exists in the Virtual DataPort database, the procedure will drop the view and create it again. The default value is
falseso if the view already exists, the procedure will fail.
options(optional): options to modify the default value of some properties of the
CREATE REMOTE TABLEcommand. Format:
'option1=value1, option2=value2, ...'. See CREATE REMOTE TABLE Command to get information about the options available.
Stored Procedure Result
The procedure returns three rows with the status of each step. For example:
Step 1 of 3: Created remote table ‘<remote table name>’ successfully.
Step 2 of 3: Inserted 2 rows into remote table ‘<remote table name>’.
Step 3 of 3: Created base view ‘<base view name>’ successfully in the ‘<vdp database name>’ database.
If the target database is based on HDFS (Hadoop, Impala, Hive), you have to enable bulk data load on the data source before executing this procedure.
This procedure only works for JDBC data sources whose adapter is supported by the Cache Engine (list of databases supported by the Cache Engine).
The user needs these privileges:
Connectover the database of the JDBC data source.
Executeover the JDBC data source.
Create viewover the Virtual DataPort database in which the base view will be created.
Create folderover the database where the base view will be created, if the procedure has to create the base view on a folder and the folder does not exist.
Executeover the views referenced in the query.
The user account of the JDBC data source has to be able to create tables in the underlying database.
SELECT * FROM CREATE_REMOTE_TABLE() WHERE datasource_database_name = 'common_sources' AND datasource_name = 'ds_jdbc_oracle' AND datasource_catalog = '' AND datasource_schema = 'REPORTING' AND remote_table_name = 'reporting_customer360_state_ca' AND replace_remote_table_if_exist = true AND query = 'SELECT * FROM customer WHERE state = ''CA''' AND base_view_database_name = 'customer360' AND base_view_name = 'customer360_state_ca' AND base_view_folder = '/reporting_customer' AND replace_base_view_if_exist = false;
Note that because
query is a literal, the single quotes have to be escaped.
This example does the following:
It checks if in the schema “REPORTING”, the database of the data source “ds_jdbc_oracle” has the table “reporting_customer360_state_ca”. If it does, it deletes this table.
In the same schema, it creates the table “reporting_customer360_state_ca” to store the results of “query”.
Executes the query and inserts the result on this table.
Creates the folder “/reporting_customer”.
It creates the JDBC base view “customer360_state_ca” in this folder that queries the table “reporting_customer360_state_ca” of the database of the data source “ds_jdbc_oracle”.
Virtual DataPort Administration Tool
When you open a base view that was created with this procedure, you will see the source query in the box Data load query, at the bottom of the dialog.
Also, in the tab Metadata of the Edit dialog of a view.