...
Two issues were reported regarding the mapping of extensions in streaming translators
1. XPanels don't show some fields from the selected table.
The problem only happened if the columns had specific constraints on them. (C, O, V)
It was resolved by removing that condition in the code. All the columns are shown now.
2. the extract includes had "UPDATE_DATE" and "UPDATE_SOURCE" fields added to them.
These two columns are redundant, we made sure to remove them from the mapping
This issue was tracked as Item IWSItem IWS-650
EJM Monitoring tool Issues with Delta Profiles and Running of Extracts
Regression issue was detected in the previously published version - maintenance tab would not show any entries.
The issue was related to the changes done in EagleML include files, due to which Monitoring Tool was not able to determine the version of Core release.
The problem was fixed by changing the way MT determines the version. It now fetches the version from eagle_product_version table, and does not depend on any EagleML configuration.
This issue was tracked as Item IWS-684
...
Ability to add native code to EagleML destinations has been added to non-streaming translators
The functionality is same as we have in XSLT and streaming translators for EagleML output data.
This issue was tracked as Item IWS-619
...
In the past Raw Service launched steps for all the existing models in XML feed even if some models were missing in a source file.
This created a lot of noise due to false errors, which should be ignored.
In order to fix this issue we added a condition to execute "rs_load" step in XML Raw Service workflow.
After the change, any load which does not have corresponding soucre file would be skipped.
This issue was tracked as Item IWS-682
...