In this section, you can figure out how to show the arrangement of a specific information base through OrientDB order line. This order is pertinent for both neighborhood and distant data sets.
Arrangement data contains default store either empowered or not, the size of that reserve, the heap factor esteem, max memory for map, hub page size, pool least and greatest size, and so forth
The accompanying assertion is the essential grammar of the config information base order.
CONFIG
Note − You can utilize this order exclusively in the wake of associating with a specific information base.
Example
In this model, we will utilize a similar information base named 'demo' that we made in the past section.
You can utilize the accompanying order to show the arrangement of demo data set.
Orientdb {db = demo}> CONFIG
In the event that it is effectively executed, you will get the accompanying yield.
LOCAL SERVER CONFIGURATION:
+---------------------------------------+-------------------------+
| NAME | VALUE |
+---------------------------------------+-------------------------+
| environment.dumpCfgAtStartup | false |
| environment.concurrent | true |
| environment.allowJVMShutdown | true |
| script.pool.maxSize | 20 |
| memory.useUnsafe | true |
| memory.directMemory.safeMode | true |
| memory.directMemory.trackMode | false |
|……………………………….. | |
| storage.lowestFreeListBound | 16 |
| network.binary.debug | false |
| network.http.maxLength | 1000000 |
| network.http.charset | utf-8 |
| network.http.jsonResponseError | true |
| network.http.json | false |
| tx.log.fileType | classic |
| tx.log.synch | false |
| tx.autoRetry | 1 |
| client.channel.minPool | 1 |
| storage.keepOpen | true |
| cache.local.enabled | true |
+---------------------------------------+-------------------------+
orientdb {db = demo}>
In the above rundown of arrangement boundaries, on the off chance that you need to change any of the boundary esteem, at that point you can do it from the order line effectively utilizing config set and get order.
Config Set
You can refresh the setup variable incentive by utilizing the CONFIG SET order.
The accompanying assertion is the fundamental linguistic structure of the config set order.
CONFIG SET <config-variable> <config-value>
Note − You can utilize this order simply subsequent to associating with a specific information base.
Example
In this model, we will utilize a similar data set named 'demo' that we made in the past section. We will adjust the 'tx.autoRetry' variable incentive to 5.
You can utilize the accompanying order to set the arrangement of demo data set.
orientdb {db = demo}> CONFIG SET tx.autoRetry 5
On the off chance that it is effectively executed, you will get the accompanying yield.
Local configuration value changed correctly
Config Get
You can show the setup variable incentive by utilizing the CONFIG GET order.
The accompanying assertion is the fundamental punctuation of the config get order.
CONFIG GET <config-variable>
Note − You can utilize this order simply subsequent to interfacing with a specific data set.
Example
In this model, we will utilize a similar information base named 'demo' that we made in the past section. We will attempt to recover the 'tx.autoRetry' variable worth.
You can utilize the accompanying order to show the arrangement of demo data set.
orientdb {db = demo}> CONFIG GET tx.autoRetry
In the event that it is effectively executed, you will get the accompanying yield.
Local configuration: tx.autoRetry = 5
