This topic describes how to replace Lightning with Hologres for data development.
Background information
Lightning is an interactive search service provided by MaxCompute. You can use Lightning to query data in MaxCompute projects based on PostgreSQL statements.
Lightning uses a shared cluster where multiple users share resources. When multiple users concurrently query a large amount of data, the query performance may deteriorate and query requests may be queued up for resources. The queries sometimes are time-consuming. In addition, Lightning does not support queries by index. To resolve the preceding issues, you can use Hologres to replace Lightning.
- Supports resource segregation among users so that queries performed by different users do not affect each other.
- Integrates seamlessly with the big data ecosystem and allows you to analyze and process petabytes of data with high concurrency and low latency.
- Integrates seamlessly with MaxCompute at the underlying layer and allows you to use foreign tables to directly query data from MaxCompute.
- Supports using indexes to query MaxCompute data imported to Hologres, providing much better performance than other open source interactive search systems.
- Provides the Java Database Connectivity (JDBC) or Open Database Connectivity (ODBC) driver that allows you to use Business Intelligence (BI) tools to analyze data from multiple dimensions.
Comparison between Hologres and Lightning
Category | Item | Hologres | Lightning |
---|---|---|---|
Feature | Supported syntax | PostgreSQL 11 | PostgreSQL 8.2 |
Data query based on internal tables | Supported | Not supported | |
Real-time data write | Supported | Not supported | |
Data query based on foreign tables | Supported | Supported | |
Parameter optimization | Custom parameter adjustment | Supported. For example, you can adjust database or user parameters based on your business requirements. | Not supported |
Number of development tools concurrently connected to each instance, which reflects the number of queries per second | Increases in a linear manner with the volume of available resources. | Is fixed to 20. | |
Internal table | Using data definition language (DDL) statements to add, modify, and delete tables | Supported | Not supported |
Data update | Supported | Not supported | |
Writing real-time data in real time | Supported | Not supported | |
Foreign table | Loading of the Meta module | Responds to queries in milliseconds. | Consumes more time if the number of MaxCompute tables increases, slowing down queries. |
Data type | Supports the following data types:
|
Only supports basic data types. | |
Performance | Engine |
|
N/A |
Resource | Supports resource segregation among users to provide stable query performance. | Does not support resource segregation among users, which is prone to latency and performance deterioration during queries. |
Procedure
