All Products
Search

This Product

    Hologres:import maxcompute data to hologres using a visual interface

    Document Center

    Hologres:import maxcompute data to hologres using a visual interface

    Last Updated:Feb 05, 2026

    This topic describes how to quickly import MaxCompute data using HoloWeb’s visual interface.

    Prerequisites

    You have logged on to a Hologres instance. For more information, see Log on to an instance.

    Background information

    HoloWeb supports one-click synchronization of MaxCompute data. You can use the visual interface to import MaxCompute table data and query it. This method delivers better performance than directly querying MaxCompute data by creating a foreign table.

    Procedure

    1. Log on to the Hologres management console.

    2. In the top navigation bar, select a region.

    3. Click Go to HoloWeb to open the HoloWeb developer page.

    4. Go to the Import MaxCompute Data page.

    5. On the HoloWeb development page, in the top menu bar, select Metadata Management > MaxCompute Query Acceleration, then click Import MaxCompute Data.

      Note

      Alternatively, select Data Solutions > Import MaxCompute Data, then click Create MaxCompute Data Import Task.

    6. On the Create MaxCompute Data Import Task page, configure the parameters.

      Category

      Parameter

      Description

      Select instance

      Instance name

      The name of the logged-on instance.

      MaxCompute source table

      Project name

      The name of the MaxCompute project.

      Schema Name

      The schema name of MaxCompute. For MaxCompute projects that use a two-layer model, this field is hidden by default. For MaxCompute projects that use a three-layer model, you can select any authorized schema under the current project from the drop-down list.

      Table name

      The name of the MaxCompute table. Supports fuzzy search based on prefixes.

      Hologres target table

      Database name

      Select the name of the Hologres database where the internal table resides.

      Schema Name

      The schema name of Hologres.

      The default is the public schema. You can also select other authorized schemas.

      Table name

      The name of the new Hologres internal table.

      After you select a MaxCompute table, the MaxCompute table name is automatically populated. You can also manually rename it.

      Target table description

      The description of the new Hologres internal table. You can customize it.

      Parameter settings

      GUC parameters

      Enter the GUC parameters to configure. For more information, see GUC parameters.

      Import settings

      Fields

      The MaxCompute table fields to import.

      You can choose to import some or all fields.

      Partition configuration

      • Partition field

        Select a partition field. Hologres creates the table as a partitioned table by default.

        Hologres supports only first-level partitions. To import multi-level partitions from MaxCompute, you only need to configure a first-level partition in Hologres. The remaining partitions are automatically mapped to regular fields in Hologres.

      • Data timestamp

        If the MaxCompute table uses dates for partitioning, select a specific partition date. The system imports data for the specified date to the MaxCompute table.

      Index configuration

      • Storage mode

        • Column-oriented Storage, suitable for various complex queries.

        • Row-oriented Storage, suitable for point queries and scans based on primary keys.

        • Row-column Storage, supports all row store and column store scenarios, along with non-primary key point queries.

        If you do not specify a storage mode, the default is Column-oriented Storage.

      • Table data lifecycle

        The lifecycle of table data. The default is Permanent storage.

        After you specify a lifecycle, if data is not modified within the specified time, the engine deletes the data after it expires.

      • Binlog

        Specifies whether to enable Binlog. For more information, see Subscribe to Hologres Binlog.

      • Binlog lifecycle

        The TTL of Binlog. The default is 30 days, which is 2,592,000 seconds.

      • Distribution columns

        Hologres shuffles data to shards based on the specified distribution columns. The same values are in the same shard. Using distribution columns as filter conditions improves execution efficiency.

      • Segment columns

        Specify some columns as segment keys. When a query condition includes segment columns, you can quickly find the storage location of the corresponding data using segment keys.

      • Clustering columns

        Specify some columns as clustering keys. The index type is closely related to the column order. Clustering indexes help accelerate range and filter queries on index columns.

      • Dictionary encoding columns

        Hologres supports building dictionary mappings for specified column values. Dictionary encoding converts string comparisons to numeric comparisons, accelerating Group By and Filter queries.

        By default, all text columns are set as dictionary encoding columns.

      • Bitmap columns

        Hologres supports building bit encoding in bitmap columns. Bitmap columns can quickly filter data within fields based on specified conditions.

        By default, all text columns are set as bitmap columns.

      SQL Script automatically parses the SQL statement for the current visual operation.

    7. Click Submit in the upper-right corner.