Development platform settings

Permissions

To configure the development platform, you need the Manage Development Platform Settings permission or be a Super Administrator or System Administrator.

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.

Directory permissions

Permission control: This setting is disabled by default. When you enable it, you can set the visibility of top-level directories for offline compute tasks to Public or Visible to Specified Members Only. This controls who can see the directory and its nested tasks. If disabled, this setting invalidates all custom directory visibility settings, and all project members can view the nested offline compute tasks.

When releasing an object across tenants, the Permission control setting of the target environment takes precedence if it differs from the source.

Edit lock

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

   Parameter	Description
   Exclusive edit lock	When disabled, users can override each other's locks. When enabled, other users cannot edit a locked object until the lock is released manually or expires. They can acquire the lock to begin editing only after it is released.
   Lock duration	If a user is inactive for the specified lock duration, the system releases the exclusive lock, making it available to other users. The default duration is 30 minutes. The minimum is 5 minutes, and the maximum is 120 minutes.
   Auto-release upon closing object	Automatically releases the lock when a user closes the object's editor tab.
   Auto-release upon successful submission	Automatically releases the lock after a successful submission. The lock is not released if the submission fails.

2. Click OK to save your settings.

   To revert to the initial system configuration, you can click Restore Defaults.

Node and task settings

1. In the Node and Task Settings section, click the Edit icon to configure default scheduling times for new tasks and object submission rules.

   • New

     Parameter		Description
     Default priority		The default priority for new integration tasks, compute tasks, and logical table tasks. Options are Lowest, Low, and Medium. The default is Medium.
     Default scheduling time	Random within 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. Valid times are from 00:00 to 23:59 in hh:mm format. The random interval must be an integer from 1 to 30.
     	Fixed time	The default time is 00:00. Valid times are from 00:00 to 23:59 in hh:mm format.
     Default Python version		The default Python version for new Python compute tasks, new Python offline compute templates, and third-party Python package installations. Options are Python 2.7, Python 3.7, and Python 3.11. The default is Python 3.7.

     Note

     • For the MaxCompute compute engine, the Default Scheduling Time is set to Fixed Time by default. You can change it to Random within Interval.

     • When you create a new offline task, such as an integration task, compute task, or logical table, the scheduling time is automatically set based on this configuration.

       • If the default scheduling time is set to Random within Interval, a random time is assigned based on the specified rule.

       • If the default scheduling time is set to Fixed Time, the specified time is used.

   • Run

     Hide logview URL when SQL contains global variables for account and password: Global variables for accounts and passwords in SQL code are displayed in plain text in the MaxCompute logview, which can create security risks. This option is disabled by default.

     If you enable this configuration item, the logview URL for SQL statements in MAXCOMPUTE_SQL and logical table tasks that reference a global variable for an account and password will be hidden in the run and data preview logs of the development environment and the O&M logs of the production environment. The logview URL is replaced with The logview URL is hidden because the current SQL statement uses the global variable "{dp_glb_xxx}", which is of the account and password type..

     Note

     This option is available only when the compute engine is MaxCompute.

   • Submit

     Parameter	Description
     Auto-parse dependencies for offline object submission	When enabled, the system automatically parses dependencies and updates the list of upstream dependencies every time you submit an offline development object, such as an SQL compute task or a logical table task. This helps prevent users from forgetting or missing upstream dependencies.
     Validate field types for logical table submission	When enabled, the system validates whether the return type of a field's calculation logic is compatible with the defined field type during logical table submission. If the types do not match, the submission is blocked. This prevents implicit type conversions that can cause data errors.

   • Decommission and delete

     Allow deleting published objects in development environment: When enabled, objects that have already been released to the production environment (such as compute tasks, integration tasks, logical tables, atomic metrics, business qualifiers, and derived metrics) can be deleted directly from the development environment.

     Important

     Objects cannot be recovered after deletion. If you delete an object in the development environment but do not release the corresponding deletion task to the production environment, you cannot apply changes to the production object because its development counterpart no longer exists.

   • Default dependency period and policy

     You can modify the default dependency period and default dependency policy.

     • Default dependency period: You can select Current Cycle (Today), Previous Cycle (Previous Day), Last 24 Hours, or Previous N Days. For Previous N Days, N defaults to 2 and cannot be empty.

     • Default dependency policy: You can select First Instance, Latest Instance, All Instances, or Last Instance.

     The initial default dependency period and policy are shown in the following table.

     Current node scheduling cycle	Upstream node scheduling cycle	Upstream node self-dependency	Default dependency period	Default dependency policy
     Daily/Weekly/Monthly	Daily	Yes/No	Current Cycle (Today)	Last Instance
     Daily/Weekly/Monthly	Hourly/Minutely	No	Current Cycle (Today)	All Instances
     Daily/Weekly/Monthly	Hourly/Minutely	Yes	Current Cycle (Today)	Last Instance
     Monthly/Weekly/Daily/Hourly/Minutely	Monthly/Weekly	Yes	Current Cycle (Today)	Last Instance
     Monthly/Weekly/Daily/Hourly/Minutely	Monthly/Weekly	No	Current Cycle (Today)	Last Instance
     Hourly/Minutely	Daily	Yes/No	Current Cycle (Today)	Last Instance
     Hourly/Minutely	Hourly/Minutely	Yes/No	Current Cycle (Today)	Last Instance

   • Tag value

     Manage the values for task tags. You can click Add Tag to add a new tag, up to a maximum of 50 tags. The tag name can contain any characters and must be 64 characters or less.

     You can click the Delete icon to remove an existing tag. If you delete a tag, it is removed from all tasks that use it. If you re-add a tag with the same name, it is restored on those tasks.

2. After you finish configuring the settings, click OK.

   To revert to the initial system configuration, you can click Restore Defaults.

Table management settings

1. In the Table Management Settings section, click the Edit icon to configure Auto-create item to be released for table deletion via SQL and Create item to be released for table deletion in Table Management.

   • Auto-create item to be released for table deletion via SQL: Enabled by default. When enabled, the system automatically creates an item to be released for table deletion when you run a drop table statement in an ad-hoc query or SQL compute task in the development environment. If this is disabled, no item to be released is created when you run a drop table table_name statement in the development environment.

   • Create item to be released for table deletion in Table Management: Enabled by default. When enabled, the system creates a corresponding item to be released when you delete a table in Table Management. If this is disabled, no item to be released is created.

2. Configure the default storage format and default external table storage format. The supported formats vary by compute engine, as shown in the following table.

   Note

   • You can configure the default external table storage format only when the compute engine is MaxCompute.

   • In the following table, - indicates that the format is not supported.

   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 the MaxCompute compute engine. The default value is empty, which means no lifecycle is set. You can enter an integer from 1 to 36,500 or quickly select 7, 14, 30, or 360 days.

   Note

   This setting is available only for the MaxCompute compute engine.

4. After you finish configuring the settings, click OK.

   To revert to the initial system configuration, you can click Restore Defaults.

Query acceleration

Enable or disable MCQA query acceleration. When enabled, all ad-hoc MaxCompute SQL queries and all SQL cell queries in the analytics platform can use MCQA query acceleration. When disabled, the current tenant cannot use MCQA query acceleration.