You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 13, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: 3.6/appendix-glossary.md
+28-8Lines changed: 28 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,25 +36,36 @@ A database contains its own collections (which cannot be accessed from other dat
36
36
37
37
There will always be at least one database in ArangoDB. This is the default database, named _system. This database cannot be dropped, and provides special operations for creating, dropping, and enumerating databases. Users can create additional databases and give them unique names to access them later. Database management operations cannot be initiated from out of user-defined databases.
38
38
39
-
When ArangoDB is accessed via its HTTP REST API, the database name is read from the first part of the request URI path (e.g. /_db/_system/...). If the request URI does not contain a database name, the database name is automatically derived from the endpoint. Please refer to [DatabaseEndpoint](http/database-database-endpoint.html) for more information.
39
+
When ArangoDB is accessed via its HTTP REST API, the database name is read from the first part of the request URI path (e.g. `/_db/myDB/`). If the request URI does not contain a database name, it defaults to `/_db/_system`.
40
40
41
41
Database Name
42
42
-------------
43
43
44
-
A single ArangoDB instance can handle multiple databases in parallel. When multiple databases are used, each database must be given a unique name. This name is used to uniquely identify a database. The default database in ArangoDB is named _system.
44
+
Each database must be given a unique name. This name is used to uniquely
45
+
identify a database.
45
46
46
-
The database name is a string consisting of only letters, digits and the _ (underscore) and - (dash) characters. User-defined database names must always start with a letter. Database names is case-sensitive.
47
+
The database name is a string consisting of only letters, digits, underscore
48
+
(`_`) and dash (`-`) characters. User-defined database names must always start
49
+
with a letter.
50
+
51
+
Database names are case-sensitive.
47
52
48
53
Database Organization
49
54
---------------------
50
55
51
-
A single ArangoDB instance can handle multiple databases in parallel. By default, there will be at least one database, which is named _system.
56
+
A single ArangoDB instance can handle multiple databases in parallel. By default,
57
+
there will be at least one database which is named `_system`.
52
58
53
-
Databases are physically stored in separate sub-directories underneath the database directory, which itself resides in the instance's data directory.
59
+
With the MMFiles storage engine, databases are
60
+
physically stored in separate sub-directories underneath the database directory,
61
+
which itself resides in the instance's data directory.
54
62
55
-
Each database has its own sub-directory, named database-<databaseid>. The database directory contains sub-directories for the collections of the database, and a file named parameter.json. This file contains the database id and name.
63
+
Each database has its own sub-directory, named `database-<database id>`. The
64
+
database directory contains sub-directories for the collections of the database,
65
+
and a file named parameter.json. This file contains the database id and name.
56
66
57
-
In an example ArangoDB instance which has two databases, the filesystem layout could look like this:
67
+
In an example ArangoDB instance which has two databases, the filesystem layout
68
+
could look like this:
58
69
59
70
```
60
71
data/ # the instance's data directory
@@ -68,7 +79,16 @@ data/ # the instance's data directory
68
79
collection-<id>/ # directory containing data about a collection
69
80
```
70
81
71
-
Foxx applications are also organized in database-specific directories inside the application path. The filesystem layout could look like this:
82
+
With the RocksDB storage engine,
83
+
data is physically stored in `.sst` files in a sub-directory `engine-rocksdb`
84
+
that resides in the instance's data directory. A single file can contain
85
+
documents of various collections and databases.
86
+
87
+
ArangoSearch stores data in database-specific directories underneath the
88
+
`databases` folder.
89
+
90
+
Foxx applications are also organized in database-specific directories inside the
91
+
application path. The filesystem layout could look like this:
Copy file name to clipboardExpand all lines: 3.7/appendix-glossary.md
+17-21Lines changed: 17 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,39 +36,35 @@ A database contains its own collections (which cannot be accessed from other dat
36
36
37
37
There will always be at least one database in ArangoDB. This is the default database, named _system. This database cannot be dropped, and provides special operations for creating, dropping, and enumerating databases. Users can create additional databases and give them unique names to access them later. Database management operations cannot be initiated from out of user-defined databases.
38
38
39
-
When ArangoDB is accessed via its HTTP REST API, the database name is read from the first part of the request URI path (e.g. /_db/_system/...). If the request URI does not contain a database name, the database name is automatically derived from the endpoint. Please refer to [DatabaseEndpoint](http/database-database-endpoint.html) for more information.
39
+
When ArangoDB is accessed via its HTTP REST API, the database name is read from the first part of the request URI path (e.g. `/_db/myDB/`). If the request URI does not contain a database name, it defaults to `/_db/_system`.
40
40
41
41
Database Name
42
42
-------------
43
43
44
-
A single ArangoDB instance can handle multiple databases in parallel. When multiple databases are used, each database must be given a unique name. This name is used to uniquely identify a database. The default database in ArangoDB is named _system.
44
+
Each database must be given a unique name. This name is used to uniquely
45
+
identify a database.
45
46
46
-
The database name is a string consisting of only letters, digits and the _ (underscore) and - (dash) characters. User-defined database names must always start with a letter. Database names is case-sensitive.
47
+
The database name is a string consisting of only letters, digits, underscore
48
+
(`_`) and dash (`-`) characters. User-defined database names must always start
49
+
with a letter.
50
+
51
+
Database names are case-sensitive.
47
52
48
53
Database Organization
49
54
---------------------
50
55
51
-
A single ArangoDB instance can handle multiple databases in parallel. By default, there will be at least one database, which is named _system.
52
-
53
-
Databases are physically stored in separate sub-directories underneath the database directory, which itself resides in the instance's data directory.
54
-
55
-
Each database has its own sub-directory, named database-<databaseid>. The database directory contains sub-directories for the collections of the database, and a file named parameter.json. This file contains the database id and name.
56
+
A single ArangoDB instance can handle multiple databases in parallel. By default,
57
+
there will be at least one database which is named `_system`.
56
58
57
-
In an example ArangoDB instance which has two databases, the filesystem layout could look like this:
59
+
Data is physically stored in `.sst` files in a sub-directory `engine-rocksdb`
60
+
that resides in the instance's data directory. A single file can contain
61
+
documents of various collections and databases.
58
62<
325A
/code>
59
-
```
60
-
data/ # the instance's data directory
61
-
databases/ # sub-directory containing all databases' data
62
-
database-<id>/ # sub-directory for a single database
63
-
parameter.json # file containing database id and name
64
-
collection-<id>/ # directory containing data about a collection
65
-
database-<id>/ # sub-directory for another database
66
-
parameter.json # file containing database id and name
67
-
collection-<id>/ # directory containing data about a collection
68
-
collection-<id>/ # directory containing data about a collection
69
-
```
63
+
ArangoSearch stores data in database-specific directories underneath the
64
+
`databases` folder.
70
65
71
-
Foxx applications are also organized in database-specific directories inside the application path. The filesystem layout could look like this:
66
+
Foxx applications are also organized in database-specific directories but inside
67
+
the application path. The filesystem layout could look like this:
0 commit comments