Redshift Templates - the "Check if Table Exists" action does not work when there are variables in the schema load mask
Redshift Templates - parallelism issues when the templates are used mutliple time in one process
Addition of demonstration project for Amazon Component usage
Microsoft Azure Storage and Amazon S3 Bucket nodes available in the workspace are now proposed automatically in Snowflake Metadata in External Storage attribute
When performing a getFile operation with S3 TOOL, if the local folder defined in the “Local File Path” does not exists then the tool will now automatically create it
Amazon Redshift technology - add delimiters around Reserved words
Template - Load Xml to Redshift (with copy) - new dedicated optimized Template to load data from XML to Redshift
TOOL Amazon S3 - new parameter "S3 Base Url"
Template - Integration Redshift - new parameter "Useless Update Detection Method"
TOOL Amazon S3 - add possibility to get multiple files
Template - Load File to Redshift with Copy - add support for positional file
TOOL Amazon S3 - some regions such as EU-NORTH-1 are not working
Template - Integration Redshift - Fix "Test If table exists" step to work with variables in temporary object masks
Template - LOAD Rdbms to Redshift (with COPY) - generated temporary file names may unexpectedly contain object delimiters
Removing unnecessary libraries
Templates updated - New Parameters 'Unlock Cdc Table' and 'Lock Cdc Table' to configure the behaviour of CDC tables locking
Templates updated - New parameter 'Cdc Subscriber' on Templates on which it was not handled yet
Amazon S3 - Retrieving a configured bucket name from a folder did not take the configuration into account
Load Rdbms to Redshift (with COPY) - Allow using stringDelimiter and fieldDelimiter at the same time
Redshift Metadata - unsupported datatype "Bytea" is removed from available datatypes and converted to Varchar datatype automatically
Templates updated - The 'Cdc Subscriber' parameter was ignored in some Templates on Lock / Unlock CDC steps
Tool Amazon S3 - when performing a "getfile" operation, the file copied locally (on the runtime server) remains locked after the end of the session