Development platform settings

Permissions

Requires a custom role with the Manage development platform settings permission, or the Super Admin or System Admin role.

Access the development platform

1. In the top navigation bar of the Dataphin homepage, choose Management Center > System Settings.

2. In the left-side navigation pane, choose Platform Settings > Development Platform.

Edit lock

1. In the Edit Lock section, click the edit icon, enable Exclusive Edit Lock, and configure the lock.

   Parameter	Description
   Exclusive Edit Lock	When disabled, users can override each other's locks. When enabled, a locked object cannot be edited by others until the lock is released or expires.
   Lock Duration	The lock expires after the specified inactivity period. Default: 30 minutes. Range: 5 minutes to 120 minutes.
   Automatically release when object is closed	Releases the lock when the object's edit tab is closed.
   Automatically release on successful commit	Releases the lock after a successful commit. Not released if the commit fails.

2. Click OK.

   Click Restore Defaults to reset.

Node task settings

1. In the Node task settings area, click Edit to configure default scheduling time and commit rules.

   • Creation

     Parameter		Description
     Default priority		The default priority for new integration, compute, and logical table tasks. Options: Lowest, Low, or Medium (default).
     Default scheduling time	Randomly within an interval	The default time interval is 00:00–03:00, and the default random interval is 5 minutes. The end time must be later than the start time. Format: hh:mm (00:00–23:59). The random time interval must be an integer from 1 to 30.
     	Fixed time	The default fixed time is 00:00. Format: hh:mm (00:00–23:59).
     Default Python version		Default Python version for compute tasks, offline templates, and third-party packages. Options: Python 2.7, Python 3.7 (default), or Python 3.11.

     Note

     • By default, Default Scheduling Time is set to Fixed time. You can change it to Randomly within an interval as needed.

     • When you create an offline task (integration, compute, or logical table), the scheduling time is set based on this configuration.

       • If Default Scheduling Time is set to Randomly within an interval, a random time is selected based on the configured rules.

       • If Default Scheduling Time is set to Fixed time, the configured time is used.

   • Execution

     Hide logview URL if SQL contains account and password global variables: Prevents account and password global variables in SQL from appearing in plaintext in MaxCompute logview URLs. Disabled by default.

     If you enable this option, the logview URL is hidden in execution, data preview, and O&M logs for MAXCOMPUTE_SQL and logical table tasks that use account and password global variables. The URL is replaced with: The logview url is invisible because the current SQL is using the global variable "{dp_glb_xxx}", which is of type account and password..

     Note

     Available only for the MaxCompute compute engine.

   • Commit

     Parameter	Description
     Automatically parse dependencies when committing offline development objects	When enabled, the system parses and updates upstream dependencies on each commit of offline objects (SQL compute tasks, logical table tasks). Prevents missing dependencies.
     Validate field data types on logical table commit	When enabled, validates that field calculation return types match the declared data type on logical table commit. Mismatches block the commit to prevent implicit type conversion errors.

   • Decommission and deletion

     Allow deleting published objects in the development environment: When enabled, published objects (compute tasks, integration tasks, logical tables, atomic metrics, business qualifiers, derived metrics) can be deleted from the development environment.

     Important

     Deleted objects cannot be recovered. Deleting an object in development without publishing the deletion makes the production object unmodifiable.

   • Default dependency period and policy

     Modify the Default Dependency Period and Default Dependency Policy.

     • Default Dependency Period: Options: Current period (day), Previous period (day), Last 24 hours, or N days ago. For N days ago, the default N is 2 (required).

     • Default Dependency Policy: Options: First instance, Latest instance, All instances, or Last instance.

     The initial default dependency periods and policies are as follows.

     Current node scheduling period	Upstream node scheduling period	Upstream self-dependency	Default dependency period	Default dependency policy
     Daily/Weekly/Monthly	Daily	Yes/No	Current period (day)	Last instance
     Daily/Weekly/Monthly	Hourly/Minutely	No	Current period (day)	All instances
     Daily/Weekly/Monthly	Hourly/Minutely	Yes	Current period (day)	Last instance
     Monthly/Weekly/Daily/Hourly/Minutely	Monthly/Weekly	Yes	Current period (day)	Last instance
     Monthly/Weekly/Daily/Hourly/Minutely	Monthly/Weekly	No	Current period (day)	Last instance
     Hourly/Minutely	Daily	Yes/No	Current period (day)	Last instance
     Hourly/Minutely	Hourly/Minutely	Yes/No	Current period (day)	Last instance

   • Tag values

     Manage task tag values. Click Add Tag to create a tag. Maximum: 50 tags, each up to 64 characters.

     Click Delete to remove a tag from all associated tasks. Re-adding the tag restores it.

2. After you complete the configuration, click OK.

   Click Restore Defaults to reset.

Table management settings

1. In the Table management settings area, click Edit to configure table deletion publish settings.

   • Automatically generate a pending publish item for table deletion after deleting a table using SQL: Enabled by default. Generates a pending publish item when a DROP TABLE statement runs in an ad hoc query or SQL compute task. When disabled, running DROP TABLE table_name does not generate a publish item.

   • Generate a pending publish item for table deletion when deleting a table in Table Management: Enabled by default. Generates a pending publish item when a table is deleted in Table Management. When disabled, no publish item is generated.

2. Configure the Default Storage Format or Default External Table Storage Format. Supported formats vary by compute engine.

   Note

   • Default External Table Storage Format is available only for MaxCompute.

   • In the table below, - indicates unsupported.

   Engine default

   Hudi

   Delta (Delta Lake)

   Paimon

   Iceberg

   Kudu

   Parquet

   Avro

   Rcfile

   Orc

   Textfile

   Sequencefile

   Binaryfile

   Csv

   Text

   Json

   MaxCompute

   -

   -

   -

   -

   -

   -

   Supported

   Supported

   Supported

   Supported

   Supported

   Supported

   -

   -

   -

   -

3. Configure the default lifecycle for physical and logical tables in MaxCompute. Default: empty (no lifecycle). Range: 1–36,500 days. Quick options: 7, 14, 30, or 360 days.

   Note

   Default lifecycle is available only for the MaxCompute compute engine.

4. After you complete the configuration, click OK.

   Click Restore Defaults to reset.

Query acceleration

Enable or disable MaxCompute Query Acceleration (MCQA). When enabled, MCQA applies to all ad hoc MaxCompute SQL queries and SQL unit queries in the analysis platform.