Tablestore supports compute and analysis using tools such as MaxCompute, Spark, Hive, Hadoop MapReduce, Function Compute, Flink, Presto, the Tablestore search index, and Tablestore SQL queries.
Select an analytical tool
Tablestore supports multiple data models, such as the wide table model and the time series model. The supported analytical tools vary by data model. You can choose the appropriate tool based on your scenario.
Analytical tool | Applicable model | Operation | Description |
MaxCompute | Wide table model | You can create a foreign table for a data table in Tablestore using the MaxCompute client, which lets you access the data in Tablestore. | |
Spark | Wide table model | When you use the Spark compute engine, you can access Tablestore through E-MapReduce SQL or DataFrame programming. | |
Hive or HadoopMR | Wide table model | Use Hive or Hadoop MapReduce to access data in Tablestore. | |
Function Compute | Wide table model | Use Function Compute to access Tablestore and perform real-time computing on Tablestore incremental data. | |
Flink |
| You can use Real-time Compute Flink to access source tables, dimension tables, or sink tables in Tablestore to perform real-time computing and analysis on big data. | |
PrestoDB | Wide table model | After connecting PrestoDB to Tablestore, use SQL to query and analyze data in Tablestore, write data to Tablestore, and import data into Tablestore through PrestoDB on Tablestore. | |
Tablestore search index | Wide table model | Search index uses inverted indexes and columnar storage to address complex multidimensional queries and statistical analysis for big data. When your business requires queries on non-primary key columns, multi-column combined queries, fuzzy queries, or analytics such as finding maximum/minimum values, counting rows, or grouping data, define these attributes as fields in a search index and use it to query and analyze your data. | |
Tablestore SQL query |
| SQL query provides a unified access interface for multiple data engines. With the SQL query feature, you can access Tablestore data to run complex queries and perform efficient analysis. |
Billing details
In CU mode (formerly pay-as-you-go mode), each compute engine that accesses Tablestore incurs charges based on read and write throughput. In VCU mode (formerly reserved mode), read and write requests consume VCU compute resources. For more information, see Billing overview.