3.3.3 Populate a Workspace
Populate Workspace allows to populate data from the Production workspace.
- Click Action
next to corresponding workspace and select
Populate to populate data from the Production
workspace in the Populate Workspace window.The following table provides descriptions for the fields in the Populate Workspace window.Table 3-3 Populate Workspace
Field Description Workspace Code Displays code for the workspace. Purpose Displays description for the workspace. Creation Date The date and time on which the workspace was created. Data Store Type The type of the source data. Write Mode You can either overwrite the existing data (truncate and insert) or append to the existing data. - Overwrite: In this mode, the underlying tables will be populated in truncate and followed by insert operation.
- Append: In this
mode, the underlying tables will be populated in the
append mode. The Data Load option is enabled only if
Append is selected on the Write Mode. The options
are:
- Selective: In this mode, only the tables filtered (selected in the Table level Data Filters) will be populated.
- ALL: In this mode, all the underlying tables mapped to the workspace will be populated along with the filters mentioned below for specific tables.
Data Filter- Global Level Enter the data filter that needs to be applied on all the tables selected for data sourcing. For example: If MISDATE is equal to Today, then it is applied to all tables (wherever it is available) for selected Data Sources during population. If this field is not found (MISDATE) in the tables, it is not updated.
OR
Click Use Template to select a library.
On selecting the template, any pre-filled values will be overridden with the template provided values.
Data Filter- Table level You can provide the data filters individually on the tables here. Select the table and enter the SQL filter. Note: You can provide multiple table names for the same SQL filter.
For example, there are two tables called Student and Employee in the target data source, and below filters are applied:- MISDATE as Today for Student and Employee tables
- ID as 1 for Student table
Then, Student table will be populated with MISDATE and ID filters and Employee table will be populated with only MISDATE filter.
Global filters are not applicable for those tables on which filters have been applied individually.
If the same table name is provided in more than one rows here, then filter condition is generated as a conjunction of all the provided filters.
Fetch Size Enter the Fetch size of JDBC properties for data upload. Batch Commit Size Enter the Batch Commit size of JDBC properties for data upload. Rejection Threshold The available options are : - Unlimited: Here, all the errors will be ignored during the data population.
- Custom Rejection Threshold: Enter the maximum of number of inserts that may fail for any of the selected tables. You can provide the maximum number of inserts that can fail while loading data to a given table from all the sources. In case of threshold breach, all the inserts into the particular target schema will be rolled back. However, it will continue with populating the next target schema.
You can also pass runtime values in workspace population for the user-defined parameters in Data Filter – Global/Table.Example: Table Filter /Global Filter
[{"id":1,"filter":"CUSTOMER_ID =$CUSTID and INCOME =$income and CUSTOMER_NAME =$customerName","tables":["CUSTOMERS"]}]Additional Parameters:
{"fetch_size" :10, "batch_commit_size" :1000, "rejection_threshold" :"UNLIMITED", "write_mode" :"APPEND", "dynamic_parameters": [\{"key":"$CUSTID","value":"125"} ,{"key":"$income$","value":"30000"},{"key":"$customerName","value":"Cust125"}]}The Runtime parameters can be passed as part of additional parameters json .Key = "dynamic_parameters". It will replace all the $ values in Table filter /Global Filters.