(2105) Release notes
- SNP
- Igor Strba
- Marian Vidra
New features
Support of Azure Databricks and Snowflake storage.
You can reload the data in parallel. The parallelization is done on the subrequests' level.
It is now possible to track the progress of the reload in the Request Browser.
VirtualProvides can be generated also with the report /DVD/OFF_CREATE_VP. In this report, you can also specify a custom name for the VirtualProvider.
Improvements
Speed of the repair of reloading requests was improved by cleaning up only the failed subrequest instead of all of them.
Subrequest monitor now displays the subrequests' selection, runtime, and reload status. If the subrequest is running, you can display a job log instead of an application log.
All background jobs scheduled from the DataTiering now have more meaningful names consisting of the name of the action, DataProvider’s name, and the request ID.
The archive is not read during the reporting if the query’s selection doesn't return any data from the index.
Option to give feedback via DVD button available on the DataTiering Main Screen.
Bug fixes
Repair of the offload copy phase was not deleting data for the failed subrequests from the archive.
Deletion of the failed offloading request was deleting only successful subrequests.
BW query may have returned duplicate records if the query was running at the same time as an offload/reload for the relevant DataProvider.
Queries with navigation attributes, where the characteristic had compounding InfoObjects, were not supported.
Queries with navigation attributes, where the characteristic had a reference InfoObject, were not supported.
Query filter was not applied while reading data from transparent binary storage during the reporting on navigation attributes, which led to reading the whole archive.
Master data replication was failing when the number of records to be replicated was bigger than the package size for reading the master data from the database.
It was not possible to generate a VirtualProvider for field-based ADSO if the ADSO contained currency or amount key figures with a different number of decimals places than a default value.
It was not possible to adjust a CompositeProvider if the original InfoProvider contained an unreferenced unit InfoObject.
Creation of VirtualProvider was failing when some InfoObject had transitive navigation attributes. This is not supported.
Pruning condition was updated even when the calculation view didn’t exist.
Cleanup was not done properly if the Writer failed during the reload phase.
Reload via DTP was not working for ADSO Data marts type on SAP BW750+.
Metadata was not updated if the reload via DTP failed.
Query name was trimmed when displayed in the Impact analysis step of the Wizard.
Log button in the Object adjustment step of the wizard was not displaying logs for the object adjustments.
Status of the unsupported lookup translation was red with no additional information in logs.