Versions Compared

Old Version 5

changes.mady.by.user Robert Adamec

Saved on

compared with

New Version Current

changes.mady.by.user Robert Adamec

Saved on

Key

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

New Features

...

Glue Scheduler with Trigger Delta

Note

A Dynamic Glue Scheduler is a tool for scheduling Glue extractions and is a central place for scheduling and management of all the replication jobs.
It will replace existing Trigger and Queue watchdogs, and Extraction Scheduler as it overcomes several of their limitations.

Dynamic Glue Scheduler introduced in the previous release now provides a new feature to schedule trigger delta replication jobs.

...

  • A Changelog for storage management parameters has been introduced. This feature allows you to see the history of changes in Storage Management.

  • The process of data insertion to the Snowflake table now contains a validation mechanism to guarantee data consistency.

  • Google Cloud Storage and BigQuery storage have been improved to properly work even in an unstable network environment.

Authorizations

There have been improvements in the authorization process for different parts of our system, including both Glue and Storage Management:

  • New transactions were created for Glue Scheduler (/DVD/GLS) and Glue Backup (/DVD/RL_TABLE_BACKUP) with corresponding transaction code authorizations.

  • A new Glue action called MAN_SETT was added to manage Glue Settings.

  • For storage management, a new action called EDIT_JCO was added for editing JCO Management.

Fixes

Glue Cockpit

  • The calculation of failed jobs in the Glue cockpit has been corrected.

...

  • You can optionally add the GLCHANGETIME field to a Glue table. By doing so, the Change Time rule is automatically assigned to the field. In the previous versions, the logic was not consistent for multiple scenarios. This has been corrected and the values are now consistent for all types of extraction - be it a table replication, ODO, DSO, or ADSO. The inserted GLCHANGETIME value is a timestamp in the UTC timezone.

  • The filtering of data in case of mass execution has been improved. The solution is now stable and consistent for all supported scenarios. Filters are now considered also when calculating the packages. This will prevent random size or even empty calculated packages.

  • BEx Query (BICS) mass execution was not working with a split on 2 variables. This has been corrected and the functionality now works as expected.

  • The replication was not working for a Glue table created from BEx Query with a characteristic that had a Display setting set to No Display.

...