S3 Vector Bucket: drop the storage box title from the diagram

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011UpvafvK8JpagF94MHWqwK
Chris LuandClaude Fable 5.1 committed 2026-11-04 08:48:24 -08:00
1 parent 81118d3c5f
commit 938c5fcd56
1 file changed
+2 -6
+2 -6
@@ -26,11 +26,8 @@ flowchart TB
vector["<b>vector bucket</b><br/>a table bucket with format LANCE"]
end
engine["<b>weed-vector</b><br/>exact search over the index"]
subgraph store ["stored in SeaweedFS, through the gateway's S3 API"]
direction LR
filers[("<b>filers</b><br/>file metadata")]
volumes[("<b>volume servers</b><br/>file chunks")]
end
filers[("<b>filers</b><br/>file metadata")]
volumes[("<b>volume servers</b><br/>file chunks")]
client -->|"S3, S3 Tables and S3 Vectors requests"| gateway
gateway --> normal
gateway --> table
@@ -44,7 +41,6 @@ flowchart TB
class gateway s3server
class client,normal,table,vector,engine,filers,volumes other
style buckets fill:none,stroke:#94a3b8
style store fill:none,stroke:#94a3b8
```
The gateway serves all three bucket kinds on the S3 port. A vector bucket is a table bucket with format `LANCE`; each index is one Lance dataset under `s3://<bucket>/vector/<index>/`. `weed-vector` reads and writes it through the gateway's S3 API, and the gateway, as for any S3 request, keeps the file metadata on the filers and the chunks on the volume servers.