Page History

Versions Compared

Old Version 1

changes.mady.by.user Unknown User (admin)

Saved on 24 Oct, 2017

compared with

New Version 2

changes.mady.by.user Unknown User (admin)

Saved on 24 Oct, 2017

Key

This line was added.
This line was removed.
Formatting was changed.

Table of Contents

class	contents

Overview

The output step is required in order to save your transformed data to a database table. To configure this step, you will need to configure a number of different settings in relation to the target database, target table, the type of update that is required, and the fields that will be mapped.

...

Understanding the Options

Anchor
tablecreationoptions
tablecreationoptions

Table Creation Options

Table Creation Type	Description
Use Existing	With this selection, the data will be written into an existing table that you select.
Create If Not Exists	If the specified table doesn’t exist in the database, then create a new one, but if it does (or once it has been created) save content into it.
Drop Existing	Always delete the existing table and create a new one. Only use this option when you know that the old data does not need to be retained.
Drop If Metadata Conflict	If there is a metadata conflict between the data in the flow and the table (such a conflict could refer to different number of fields/columns in the flow file than in the table or possibly a different data type), then delete the table and create a new one to store data; otherwise if the metadata matches without there being a conflict, use the existing table. Only use this option when you know that the old data does not need to be retained.

...

Note
In rarer circumstances, the target tables may not exist in advance. In these cases Yellowfin can create the table for you, provided you have the right security access. The Create if Not Exists option will create the table if it does not exist. Typically this will only happen the first time a flow is run, after which the existing table will be used. The Drop Existing will always delete and re-create the table, thus deleting any data that may have been stored in that table - and should be used with caution. Similarly the Drop if Meta-Data Conflict will drop and re-create the table if there is a mismatch between the table structure and the data contained in the flow. This option is also destructive to data and should be used with caution.

Note

In rarer circumstances, the target tables may not exist in advance. In these cases Yellowfin can create the table for you, provided you have the right security access. The Create if Not Exists option will create the table if it does not exist. Typically this will only happen the first time a flow is run, after which the existing table will be used. The Drop Existing will always delete and re-create the table, thus deleting any data that may have been stored in that table - and should be used with caution. Similarly the Drop if Meta-Data Conflict will drop and re-create the table if there is a mismatch between the table structure and the data contained in the flow. This option is also destructive to data and should be used with caution.

Anchor

	updateoptions
	updateoptions

Update Type

Update Type	Description
Insert	To append or add data to the end of the existing data.
Truncate	To replace all the existing data with the new values. This should be used with caution as it will delete any existing data.
Update	Update the value of fields in the database table where a matching row exists in the transformation flow. This option overwrites existing data and should be used with caution.
Update & Insert	Update the value of fields in the database table where a matching row exists in the transformation flow. This option overwrites existing data and should be used with caution. If not matching row exists then insert a new row.

...

How to Configure an Output Step

Choose database from the list. Only writeable data sources will be shown.
Choose a table creation option. Click here to understand the table creation options.

Image Added
Continue with the selected process:
1. If Use Existing was selected, select a pre-existing table to write data into. Then skip to step 4
(update type selection)
1. .
2. If Create If Not Exists was selected, then enter a new table name. You can optionally select any table fields that you would like to index (note: indexes are used to improve query performance. If in doubt about this option, please contact your system administrator). Move on to step 4.
  
  Image Added
3. If Drop Existing was selected, then enter a new table name. Move on the step 5.
4. If Drop if Metadata Conflicts was selected, then enter a new table name, also specify whether the existing table is to be dropped in case there are more fields in the transformation flow than in the table. Then skip to step 4.
Choose an update type to indicate how the table will be updated. Click here to understand all the options.

Note
For Update and Update & Insert options, additional row matching is required. This is done by
choosing
choosing Join
for
for the identifier or matching field, and
then
then Set
to
to indicate which field to update. If no option is selected, the field will not be used in the join or be updated as part of the flow.
Enable the button to run this flow IF in preview mode. SEE WARNING NOTE.

Image Added
Once the configuration is done, click on the Apply button to save these changes.

Note
For Update and Update & Insert options, additional row matching is required. This is done by

...

Content

Space Tools