mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2024-01-19 02:48:24 +00:00
49 lines
966 B
Markdown
49 lines
966 B
Markdown
##arangodb
|
|
|
|
database: https://github.com/arangodb/arangodb
|
|
go driver: https://github.com/arangodb/go-driver
|
|
|
|
|
|
options:
|
|
|
|
```
|
|
[arangodb]
|
|
enabled=true
|
|
db_name="seaweedfs"
|
|
servers=["http://localhost:8529"]
|
|
user="root"
|
|
pass="test"
|
|
|
|
# whether to enable fulltext index
|
|
# this allows for directory prefix query
|
|
fulltext=true
|
|
|
|
# tls settings
|
|
insecure_skip_verify=true
|
|
```
|
|
|
|
supports buckets with an extra field in document.
|
|
omitempty means extra space is not used.
|
|
|
|
i test with
|
|
`docker run -p 8529:8529 -e ARANGO_ROOT_PASSWORD=test arangodb/arangodb:3.9.0`
|
|
|
|
|
|
## todo
|
|
|
|
implement native TTL
|
|
|
|
|
|
## thoughts
|
|
|
|
should there be one collection per bucket? would make deleting a bucket instant as compared to fast
|
|
|
|
|
|
## comparison
|
|
|
|
arangodb uses rocksdb in the background, so i am assuming things run in log time
|
|
|
|
single document retreval might run in constant time
|
|
|
|
i am not sure how the prefix query scales compared to the recursive calls that some other stores do for folder deletion
|