forked from crate/crate
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathset.txt
More file actions
53 lines (34 loc) · 1.27 KB
/
Copy pathset.txt
File metadata and controls
53 lines (34 loc) · 1.27 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
.. highlight:: psql
.. _ref-set:
===========
SET / RESET
===========
Alter and restore global cluster setting values at runtime.
For a list of the possible settings see
:ref:`conf-cluster-settings`. Only settings documented with
*Runtime:* ``yes`` can be changed.
Synopsis
========
::
SET GLOBAL [ PERSISTENT | TRANSIENT ] setting_ident = value [ , ... ]
RESET GLOBAL setting_ident [ , ... ]
Description
===========
Using the ``SET`` and ``RESET`` statements it is possible to configure
the crate cluster at runtime.
``SET`` can be used to change a configuration setting ident to a
different value. Using ``RESET`` will reset the setting to its
default value or, if the setting was defined at the configuration
file on node start-up, to this value.
Parameters
==========
:setting_ident: The full qualified setting ident of the setting to set / reset.
:value: The value to set for the configuration setting.
Persistence
===========
The default is ``TRANSIENT``. Settings that are changed using the ``TRANSIENT``
keyword will be lost if the cluster is stopped or restarted.
Using the ``PERSISTENT`` keyword will persist the changes to disk so that the
change will survive cluster restarts.
.. NOTE::
The persistence keyword can only be used within a ``SET`` statement.