- Directly query MaxCompute data in Hologres.
You can create a foreign table mapping a specified MaxCompute table in Hologres to query data in the MaxCompute table. In this way, you do not need to import the MaxCompute data to be queried to Hologres. The data is still stored in MaxCompute. This is a preferred method, which is suitable for the scenario where the size of the data to be scanned is less than 100 GB. This is a threshold for the size of the hit partition after partition filtering, regardless of the size of the queried fields. For more information, see Create a foreign table to accelerate queries of MaxCompute data.
- Import MaxCompute data to Hologres for queries.
You can import MaxCompute data to Hologres for queries. The imported data is stored in Hologres. Compared with directly querying MaxCompute data, this method features much higher query efficiency. This method is suitable for the following scenarios: scenarios where the size of the data to be scanned in a single table is greater than 100 GB, complex queries, index-based queries, scenarios where data needs to be updated, and scenarios where INSERT operations are required. For more information, see Use SQL statements to import MaxCompute to Hologres.
Hologres seamlessly integrates with the big data ecosystem. It can directly interconnect with MaxCompute to query and analyze MaxCompute data, without the need to store the data. This allows you to quickly obtain query results. You can directly query MaxCompute data in Hologres or import MaxCompute data to Hologres for queries in different scenarios: