Change Details

@BTullis reports: > [There is an] Ops Week issue around `mw_content_merge_events_to_mw_content_history_daily.spark_process_events` > The error messages from the yarn logs don't mean much to me and they're also gigantic. > I'm using this to filter out the INFO level messages: `yarn logs -applicationId application_1757517622464_163684|grep -v INFO|less` > There are several errors shown, but possibly the most meaningful is: >> Caused by: org.apache.spark.SparkException: The ON search condition of the MERGE statement matched a single row from the target table with multiple rows of the source table. This could result in the target row being operated on more than once with an update or delete operation and is not allowed.

@BTullis reports: > [There is an] Ops Week issue around `mw_content_merge_events_to_mw_content_history_daily.spark_process_events` > The error messages from the yarn logs don't mean much to me and they're also gigantic. > I'm using this to filter out the INFO level messages: `yarn logs -applicationId application_1757517622464_163684|grep -v INFO|less` > There are several errors shown, but possibly the most meaningful is: >> Caused by: org.apache.spark.SparkException: The ON search condition of the MERGE statement matched a single row from the target table with multiple rows of the source table. This could result in the target row being operated on more than once with an update or delete operation and is not allowed. Similar to: {T397525} and {T388715}

@BTullis reports: > [There is an] Ops Week issue around `mw_content_merge_events_to_mw_content_history_daily.spark_process_events` > The error messages from the yarn logs don't mean much to me and they're also gigantic. > I'm using this to filter out the INFO level messages: `yarn logs -applicationId application_1757517622464_163684|grep -v INFO|less` > There are several errors shown, but possibly the most meaningful is: >> Caused by: org.apache.spark.SparkException: The ON search condition of the MERGE statement matched a single row from the target table with multiple rows of the source table. This could result in the target row being operated on more than once with an update or delete operation and is not allowed. Similar to: {T397525} and {T388715}