Translate release notes 1.5.0

We have shifted from using permanent tables to transient tables for those created and destroyed during application job execution. This change is designed to streamline the lifecycle of application tables and reduce consumer storage costs. Additionally, we have revised the application code to ensure that transient tables are dropped in the event of job failure.

Enhancements

  • The RUN stored procedure now includes the new parameters tgt_dentsu_client_key and src_dentsu_client_key which can be used instead of tgt_merkury_key and src_merkury_key. Both sets of parameters are currently supported, but we advise transitioning to the Dentsu client key versions as the Merkury key versions will be deprecated in the future.

  • The client_id_map_vw view now features a new dentsu_client_key column to replace the merkury_key column. Additionally, the default value in this view has been changed from CONSUMER_MERKURY_KEY to CONSUMER_DENTSU_CLIENT_KEY.
    Furthermore, key value pairs SRC_DENTSU_CLIENT_KEY and TGT_DENTSU_CLIENT_KEY have been added to the "approved_transcoding_pairs" field. Use these instead of the SRC_MERKURY_KEY and TGT_MERKURY_KEY pairs. While both options are currently supported, users are encouraged to switch to the Dentsu client key versions.

  • We have also implemented backend changes to improve the speed of onboarding new clients.

Related articles