imbajin commented on code in PR #3116:
URL: https://github.com/apache/hugegraph/pull/3116#discussion_r3652789904


##########
README.md:
##########
@@ -78,11 +78,11 @@ HugeGraph supports both **standalone** and **distributed** 
deployments:
              
┌────────────────────────────────┼────────────────────────────────┐
              │                                │                                
│
 ┌────────────▼────────────┐   ┌───────────────▼───────────────┐   
┌───────────▼──────────┐
-│    Standalone Mode      │   │      Distributed Mode         │   │   Legacy 
Backends    │
-│  ┌───────────────────┐  │   │  ┌─────────────────────────┐  │   │      
(≤v1.5)         │
-│  │      RocksDB      │  │   │  │     HugeGraph-PD        │  │   │  MySQL │ 
PostgreSQL  │
-│  │    (embedded)     │  │   │  │   (Raft, 3-5 nodes)     │  │   │  Cassandra 
          │
-│  └───────────────────┘  │   │  │      :8620/:8686        │  │   │  HBase 
(≤v1.7)       │
+│    Standalone Mode      │   │      Distributed Mode         │   │  Supported 
Backends  │

Review Comment:
   🧹 Removing the implementations should not erase the historical-version 
guidance: users can still use MySQL, PostgreSQL, Cassandra, ScyllaDB, and Palo 
with HugeGraph ≤1.5 releases. Please keep them in a separate `Historical 
Backends (≤1.5)` box rather than deleting that part of the diagram. The 
current/deprecated backends should remain in a different box, with HBase marked 
as deprecated pending removal in 2.0; the test-only Memory backend should not 
be presented as production-supported. Also please realign the ASCII boxes: the 
right border currently ends after the two backend rows and reappears as a 
detached vertical segment, so the rendered diagram has broken 
indentation/boundaries.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to