While debugging scheduled jobs, it can be hard to unmarshal the ScheduleDetails and ExecutionArgs columns in the system.schedule_jobs print file in the debug zip. We ought to create a new crdb_internal.scheduled_jobs built in that unmarshals these fields for us and sticks them in the debug zip.
In the implementation, the ScheduleDetails proto should be flattened (i.e. one column for each field in the in the proto), as all jobs share these fields, while the ExecutionArgs should be one column, type json, as each schedule type has different execution args.
While debugging scheduled jobs, it can be hard to unmarshal the
ScheduleDetails
andExecutionArgs
columns in the system.schedule_jobs print file in the debug zip. We ought to create a newcrdb_internal.scheduled_jobs
built in that unmarshals these fields for us and sticks them in the debug zip.In the implementation, the
ScheduleDetails
proto should be flattened (i.e. one column for each field in the in the proto), as all jobs share these fields, while theExecutionArgs
should be one column, type json, as each schedule type has different execution args.Jira issue: CRDB-39778