DescriptionIngest schedule execution history file into SCHEDULE_ACTIVITIES and SCHEDULE_ACTIONS tables
DocstringIngester module for the Executable Schedule file type (SCHED_HIST). The data is ingested into 2 separate tables: Acitivities and Actions This is a sample XML file which contains a schedule header and body with metadata and data. data element has entries that could be a Task, Activity or an Event as shown below: <Schedule_History domain="SGA1"> <List_of_Activities count="1"> <Activity> <Internal_Id>71fc3c25-f620-4b20-a37e-77d061fc9c1d</Internal_Id> <Name>AuthenticationMode_SGA1</Name> <Proc_Id>BUC_P1</Proc_Id> <Type>GR_ACT</Type> <Class>OAS_PE</Class> <Scheduled_Time>UTC=2022-07-12T08:40:16.279</Scheduled_Time> <Execution_Time>UTC=2022-07-12T08:40:16.279</Execution_Time> <Trigger_Time>UTC=2022-07-12T08:40:16.279</Trigger_Time> <Absolute_Orbit>9</Absolute_Orbit> <PSO>53.439</PSO> <Final_Status>Expired</Final_Status> <List_of_Parameters count="1"/> <List_of_Actions count="8"> <Action> <Timestamp>UTC=2022-07-12T08:26:27.861</Timestamp> <Message>Activity loaded from file SGA1_SCH_MPS__BUC_SCHEX______G20220712000000Z_S20220712070000Z_E20220713000000Z.xml</Message> <Status>Not Released</Status> </Action> ... </List_of_Actions> </Activity> </List_of_Activities> <List_of_Timeline_Actions count="3"> <TML_Action> <Timestamp>UTC=2022-07-12T08:26:03.115</Timestamp> <Message>SGA1 Timeline status changed to RUNNING</Message> <Status>RUNNING</Status> </TML_Action> ... </List_of_Timeline_Actions> </Schedule_History>
Wiki pageNone
Activity fileSCHEDULE_INGESTER.xml
Executablealg/schedule_ingester.py
Calling conventionfilename
Table triggers None
Scheduler triggers
  • File scan *_???_SCH_HIST_ in {settings.DATALAKE_PRIMARY}/EXEC_SCHEDULE
Output tables
Event raised None