All Products
Search
Document Center

Data Management:[Announcement] Discontinuation of Data Lake Database and Table APIs in DMS 2018-11-01

Last Updated:Feb 06, 2026

To improve the stability and performance of Data Lake database and table OpenAPIs, all Data Lake-related APIs in Data Management (DMS) version 2018-11-01 will be discontinued soon. You must migrate your API calls to the new OpenAPI version 2025-04-14 to ensure business continuity.

Effective date

March 5, 2026 at 00:00:00 (Singapore Time, UTC+8)

Details

Starting from the effective date, all Data Lake database and table-related OpenAPIs in the DMS 2018-11-01 version will be discontinued. These APIs will be replaced by equivalent or enhanced APIs in the new 2025-04-14 version.

The following APIs in the 2018-11-01 version will be discontinued:

  • Database

    • ListDataLakeDatabase

    • GetDataLakeDatabase

    • CreateDataLakeDatabase

    • UpdateDataLakeDatabase

    • DeleteDataLakeDatabase

  • Catalog (Data Catalog)

    • ListDataLakeCatalog

    • GetDataLakeCatalog

  • Table

    • ListDataLakeTablebaseInfo

    • GetDataLakeTable

    • ListDataLakeTable

    • ListDataLakeTableName

    • CreateDataLakeTable

    • UpdateDataLakeTable

    • DeleteDataLakeTable

  • Partition

    • ListDataLakePartition

    • GetDataLakePartition

    • CreateDataLakePartition

    • UpdateDataLakePartition

    • DeleteDataLakePartition

    • ListDataLakePartitionName

    • ListDataLakePartitionByFilter

    • BatchCreateDataLakePartitions

    • BatchUpdateDataLakePartitions

    • BatchDeleteDataLakePartitions

  • Function

    • ListDataLakeFunction

    • ListDataLakeFunctionName

    • GetDataLakeFunction

    • CreateDataLakeFunction

    • UpdateDataLakeFunction

    • DeleteDataLakeFunction

Impacts and recommendations

Impacts

Starting from the effective date, all calls to the 2018-11-01 version Data Lake APIs will return error responses. This will result in:

  • API call failures with error codes indicating service discontinuation.

  • Interruption of automated workflows that depend on these APIs.

  • Potential service disruption if migration is not completed before the deadline.

  • Loss of business continuity for applications that have not migrated.

Recommendations

  • Start migration immediately: Begin the migration process as soon as possible to avoid service disruptions before the March 5, 2026 deadline.

  • Switch to the new API version: Update all API calls to use version 2025-04-14.

  • Test thoroughly: Conduct comprehensive testing in development and staging environments before production deployment.

  • Refer to documentation: Consult the Alibaba Cloud API Portal for detailed interface definitions and usage examples.