You can use AQL to set and get settings for its environment in an interactive session. Additionally, some settings can be set via the command-line which is useful when you would like to run a command without opening an interactive session by using the
To get the value of a setting, run:
aql> get <setting>
<setting> is the name of the setting.
The following is an example of getting the setting for
aql> get output
OUTPUT = TABLE
To set the value of a setting, run:
aql> set <setting> <value>
<setting>is the name of the setting.
<value>is the value to change the setting to.
The following is an example of setting
aql> set output json
The available settings are:
Echo commands. Also available via the
ECHO ( TRUE | FALSE )
The output mode. Also available via the
OUTPUT ( TABLE | JSON | MUTE | RAW )
aql> set output table
Disable printing of type of the data value such as GeoJSON, LIST, MAP_KEY_ORDERED etc. The output mode. Also available via the
OUTPUT_TYPES (FALSE | TRUE)
Enable verbose output. The output mode. Also available via the
VERBOSE ( TRUE | FALSE )
The time, in milliseconds, to wait for a query to complete. Also available via the
Socket idle timeout in milliseconds for a query. Also available via the
The path to the user-managed Lua files. Also available via the
The time, in seconds, that subsequently created or updated record will live before being evicted by the server.
Enable printing of metadata (digest, ttl, generation) of the record. Valid only in JSON view.
RECORD_PRINT_METADATA (TRUE | FALSE)
Option removed as of aql 7.0.
Flag for sending the primary key lookup request to all the replicas in round-robin manner, not just master.
REPLICA_ANY (TRUE | FALSE)
Flag for sending the key to the server in read/write/delete operations.
KEY_SEND (TRUE | FALSE)
Flag for setting policy value on the underlying C API calls used by DELETE, INSERT, EXECUTE, and SELECT (when doing a scan) operations. Applicable only for server version 3.10+. See Durable Delete for details.
DURABLE_DELETE (TRUE | FALSE)
The setting values set using aql are valid only for the current session. A new invoking of aql would have the default values.