...
The storage path is created by encoding of the internal path.
For example, files in ArchiveLink-repositories are stored into following path:
Knowledge Provider/ArchiveLink/<DocId>/<CompId>
Now this It is then appended to the root folder to store and access data in the storage.
These configuration parameters control the storage path encoding:
| Note |
|---|
These configuration values must not be changed for existing repository as it will lead to data lost and inconsistency! |
Parent | Parameter | Description | Default |
|
| When set to |
|
|
| create subfolder from the base32 encoded folder name with this length, this parameter can reduce the folder depth . Available values 4, 8, 16. |
|
|
| the filename of the document encoded in base32 is maximum this long, otherwise it will be splitted in subfolders. Any number between 10 and 250 can be used. |
|
The internal path is encoded to create the storage path by following steps:
If parameter
contrepinpathis set totrue, the storage path will start with the repository name.Each directory name is Base32-encoded and the result split into blocks separately.
...
In case the length of component id exceeds the size setup by parameter maxFileNameLength, it is split into blocks of this size which get interpreted as directories with exception of the last block which is the file name. Default for maxFileNameLength is 250.
| Info |
|---|
In split file system V2, Base32-encoding and splitting is also applied to the component id. All blocks except the last are directories, the last block is the file name. |
...
.
Example: Storage path for component id data of document id 0123456789ABCDEF0123456789ABCDEF.
...
Finally, the component id data is short and used as file name:
file names
MRQXIYI.InfoandMRQXIYI.Data
| Info |
|---|
In split file system until version 2, Base32-encoding and splitting is also applied to the component id. All blocks except the last are directories, the last block is the file name. For example: Component Id
|