0. Introduction
This document is the future development plan of TuGraph, including functions under development, functions not in the development plan, functions that have been developed but not in the open source version, etc., for developers' reference to avoid repeated development.
1. Plan in detail
| The serial number | Feature | Status |
|---|---|---|
| 1 | High availability | Enterprise Edition Support |
| 2 | Attribute level permissions | Enterprise Edition Support |
| 3 | Algorithm is rich | Enterprise Edition support 30+ algorithms |
| 4 | Perfect quality structure | on-going |
| 5 | APOC Library | With partial graph algorithm, continuous improvement |
| 6 | DGL | Beta integration, testing |
| 7 | Java OGM | Under development, expected 2022.10 |
| 8 | The REST interface was migrated from cpprestsdk to brpc | In planning, expected 2022.10 |
| 9 | Multi-graph joint operation interface | In the plan, it is expected to be 2022.11 |
| 10 | The Default Value attribute is supported | In the plan, it is expected to be 2022.12 |
| 11 | TuGraph on cloud | In the plan, it is expected to be 2022.12 |
| 12 | Neo4j and other databases are migrated by one click | In the plan, it is expected to be 2023.06 |
| 13 | ISO GQL | In the plan, it is expected to be 2023.12 |
| 14 | Log system Optimization | In the plan |
| 15 | Query engine CBO optimization | In the plan |
The above plan is decided by PMC through consultation and may be modified in the future, subject to the actual progress.