Details
Major Description
Currently, when creating a shadow dataset with a filter (WHERE ....), if a failure takes place, it gets logged to the WARN logs, and is not reported by the prometheus metrics under the "cbas_failed_to_parse_records_count" metric.
However, the failure is logged properly in the dcp_ingestion_failure logs and can be queried using the dcp_ingestion_failure_report() function.
Example:
2021-08-18T19:04:37.817+03:00 WARN CBAS.runtime.ShadowStreamSelectRuntimeFactory [SA:JID:0.5:TAID:TID:ANID:ODID:1:0:2:0:0] failed to process document with key <ud>aa</ud> on analytics collection Default.myCollection due to Type mismatch: function get-item expects its 1st input parameter to be of type array or multiset, but the actual input type is string (in line 1, at column 8)
|
|
|
2021-08-18T19:04:37.819+03:00 WARN CBAS.runtime.ShadowStreamSelectRuntimeFactory [SA:JID:0.5:TAID:TID:ANID:ODID:1:0:1:0:0] failed to process document with key <ud>a</ud> on analytics collection Default.myCollection due to Type mismatch: function get-item expects its 1st input parameter to be of type array or multiset, but the actual input type is string (in line 1, at column 8)
|
|
|
2021-08-18T19:04:37.840+03:00 WARN CBAS.runtime.ShadowStreamSelectRuntimeFactory [SA:JID:0.5:TAID:TID:ANID:ODID:1:0:2:0:0] failed to process document with key <ud>aaa</ud> on analytics collection Default.myCollection due to Type mismatch: function get-item expects its 1st input parameter to be of type array or multiset, but the actual input type is string (in line 1, at column 8)
|