Storing Output of Crypto Operations in a New Column
BDT allows you to store the output of the crypto operations (encrypt/decrypt/rekey) in a new column. To enable this feature, add the targetColName parameter to the BDT policy file.
If the targetColName parameter is specified, the new column will hold the output of the crypto operations (encrypt/decrypt/rekey).
You can also add the srcColumnAction parameter to the BDT policy file to specify the action (preserve/remove/empty) to be performed on the source column.
Refer to Columns Attributes for details about the possible options regarding the srcColumnAction parameter.
Destination Types
Following are the different destination types:
Destination File
The new column is created with the same name as specified in the targetColName parameter. The case sensitivity of the new column is based on the targetColName parameter.
If the column name specified in the targetColName parameter (irrespective of the case sensitivity) exists anywhere in the input file, the transformation is interrupted and the BDT throws an error as shown below:
Column "targetColName" exists in the input file.
Destination DB
The target column name in the table will be created as per value of the caseSensitive parameter (true or false) in the BDT policy file.
Following are the possible scenarios and errors:
| Scenario | Error |
|---|---|
| The target column name already exists in the table with a different datatype. | Column "targetColName" exists in the input file. |
| The target column name already exists in the table with same datatype and length. | Column "targetColName" exists in the input file. |
Refer to Destination CSV File, Destination Fixed Length File, and Destination DB for details.
