2021/07/30¶
This section introduces new features and enhancements for July in Version 2.2.
Core Service¶
Issue | Fix / Enhancement | Impact (if any) |
---|---|---|
Data Catalog supports the free version and does not support resource expansion and contraction. | The Data Catalog resource specifications are more detailed, which include resources for synchronization, read-write, and storage, and support resource expansion and contraction adjustments. The adjusted resources will be connected to the metering service, which will show the resource usage according to the OU. | The Data Catalog resource usage reporting depends on the Data Catalog service. If the Data Catalog service does not release a patch, there might be no resource usage reported. |
IoT Hub¶
Device Connectivity and Management Service¶
Issue | Fix / Enhancement | Impact (if any) |
---|---|---|
To be able to quickly search assets using tags, there is a need to support tag searching using IN. | Added support for search using IN for the expression parameter for tags. | None. |
Alert Management Service¶
Issue | Fix / Enhancement | Impact (if any) |
---|---|---|
The CN5 alert-engine will old GC when it runs out of memory and the service is unable to run normally, which might be caused by too much measurement point cache. | Limits the measurement point cache max size (default 1,000,000) and expiration time (default 30 hours) to prevent running out of memory. | None. |
Enterprise Data Platform¶
Data Synchronization Service¶
Issue | Fix / Enhancement | Impact (if any) |
---|---|---|
After the workflow is set up and scheduled to run, its status might remain as “Running” in the workflow operation page, and is unable to end normally. | Fixed the issue where the status stays at “Running” caused by abnormal pods. The workflow can now end normally. | None. |
Application Enablement Platform¶
Business Process Management¶
Issue | Fix / Enhancement | Impact (if any) |
---|---|---|
There are issues encountered when using the Business Process Management service to orchestrate OTA scenarios, such as not being able to select a specific date time range for the OTA job to be executed. |
|
None. |