Dataphin:Manage to-be-committed instances

Section

Description

① Filter and search area

Filter to-be-committed instances by name or ID.

• Submitted by Me: Shows only instances submitted by the current user.

• Select Project: Filters instances by project. You can select multiple projects for which the current user has the O&M - Access Directory permission.

  Note

  After you filter by project, the list shows only instances from the selected projects.

• Filter: Click Filter to expand the filter options. Click Reset to clear all filter criteria and restore the defaults. The following filter options are available:

  • Scheduling Cycle: Filters by the scheduling cycle. You can select one or more options: Daily, Weekly, and Monthly.

  • Submitter: Filters by the user who submitted the instance.

  • Scheduled time: Filters for to-be-committed instances that are scheduled for Today, Today and later, or a specific time range.

  • Status: Filters instances by status. The available statuses are Instance Pending Submission, Instance Generation Failed, Paused, Submitting, and Instance Generation Succeeded.

    • Instance Pending Submission: The instance is waiting to be generated and submitted for a data backfill at its scheduled time.

      Note

      For a periodic data backfill task, the to-be-committed instance is generated at 23:00 on the day before the scheduled time.

    • Instance Generation Failed: The backfill instance could not be generated, typically due to a system error. You can rerun a to-be-committed instance with this status. For more information, see Rerun a to-be-committed instance.

    • Paused: A paused instance will not generate new runnable backfill instances. This does not affect backfill instances that have already been generated. You can resume the instance to allow generation to continue. For more information, see Resume a to-be-committed instance.

    • Submitting: The to-be-committed instance is being processed to generate a runnable backfill instance.

    • Instance Generation Succeeded: The to-be-committed instance has successfully generated a runnable backfill instance. You can view the generated instance on the Submitted Instances page. For more information, see Manage submitted instances.

② List operations

• Customize table columns: Click the icon to select which columns to display and adjust their order.

  Note

  • The first column and the Actions column cannot be hidden or reordered.

  • Column settings are reset to the default if you clear your browser's cache or switch browsers.

• Refresh list: Click the icon to refresh the current list.

③ To-be-committed instance list

Lists to-be-committed instances generated from periodic tasks, with columns such as Backfill instance name, Business date, Scheduling cycle, Scheduled time, Instance status, Submitter, Project, and Data backfill task. You can adjust column widths, which are saved in your browser and lost if you clear the cache. The available operations are:

• Save as Data Backfill Task: For a to-be-committed instance from a one-time data backfill, click the icon to save it as a data backfill task. For more information, see Create a data backfill task.

• Resume: Resumes instances that have the Paused status.

  Note

  When you resume a paused to-be-committed instance, the system checks if its scheduled time has passed. If it has, the system automatically generates the backfill instance and starts the data backfill.

• Pause: Pauses instances with the Instance Pending Submission status. Pausing prevents new runnable backfill instances from being generated but does not affect those already generated. To resume a paused instance, click the icon in its row.

• Rerun: Reruns an instance with the Instance Generation Failed status. Click the icon in its row.

④ Batch operations area

Perform actions on multiple to-be-committed instances at once.

• Batch Resume: Resume multiple to-be-committed instances at the same time.

• Batch Pause: Pause multiple to-be-committed instances at the same time.

  Note

  This action prevents new runnable backfill instances from being generated, but does not affect instances that have already been generated.