schema
stringclasses
471 values
key
stringlengths
0
203
description
stringlengths
0
4.37k
object
stringlengths
2
322k
stylecop.schema.json
elementOrder
Specifies the traits used for ordering elements within a document, along with their precedence.
{"type": "array", "default": ["kind", "accessibility", "constant", "static", "readonly"], "items": {"type": "string", "enum": ["accessibility", "kind", "constant", "static", "readonly"]}, "uniqueItems": true}
stylecop.schema.json
items
{"type": "string", "enum": ["accessibility", "kind", "constant", "static", "readonly"]}
stylecop.schema.json
systemUsingDirectivesFirst
When true, System using directives should be placed before other using directives.
{"type": "boolean", "default": true}
stylecop.schema.json
usingDirectivesPlacement
Specifies the desired placement of using directives. insideNamespace: Place using directives inside the namespace definition outsideNamespace: Place using directives outside the namespace definition preserve: Allow using directives inside or outside the namespace definition
{"type": "string", "enum": ["insideNamespace", "outsideNamespace", "preserve"], "default": "insideNamespace"}
stylecop.schema.json
blankLinesBetweenUsingGroups
Specifies if using groups should be separated by a blank line. allow: A blank line is allowed, but not required require: A blank line is required omit: A blank line is not allowed
{"type": "string", "enum": ["allow", "require", "omit"], "default": "allow"}
stylecop.schema.json
namingRules
Configuration for naming rules (SA1300-)
{"type": "object", "additionalProperties": false, "properties": {"allowCommonHungarianPrefixes": {"type": "boolean", "default": true}, "allowedHungarianPrefixes": {"type": "array", "default": [], "items": {"type": "string", "pattern": "^[a-z]{1,2}$", "uniqueItems": true}}, "allowedNamespaceComponents": {"type": "array", "default": [], "items": {"type": "string", "uniqueItems": true}}, "includeInferredTupleElementNames": {"type": "boolean", "default": false}, "tupleElementNameCasing": {"type": "string", "enum": ["camelCase", "PascalCase"], "default": "PascalCase"}}}
stylecop.schema.json
allowCommonHungarianPrefixes
Determines whether common Hungarian notation prefixes should be allowed.
{"type": "boolean", "default": true}
stylecop.schema.json
allowedHungarianPrefixes
Allowed Hungarian notation prefixes.
{"type": "array", "default": [], "items": {"type": "string", "pattern": "^[a-z]{1,2}$", "uniqueItems": true}}
stylecop.schema.json
allowedNamespaceComponents
Allowed namespace components, such as ones beginning with a lowercase letter.
{"type": "array", "default": [], "items": {"type": "string", "uniqueItems": true}}
stylecop.schema.json
includeInferredTupleElementNames
Specifies whether inferred tuple element names will be analyzed as well.
{"type": "boolean", "default": false}
stylecop.schema.json
tupleElementNameCasing
Specifies the casing convention used for tuple element names.
{"type": "string", "enum": ["camelCase", "PascalCase"], "default": "PascalCase"}
stylecop.schema.json
maintainabilityRules
Configuration for ordering rules (SA1400-)
{"type": "object", "additionalProperties": false, "properties": {"topLevelTypes": {"type": "array", "default": ["class"], "items": {"type": "string", "enum": ["class", "interface", "struct", "delegate", "enum"]}, "uniqueItems": true}}}
stylecop.schema.json
topLevelTypes
The set of type kinds which should be placed in separate files according to the type name.
{"type": "array", "default": ["class"], "items": {"type": "string", "enum": ["class", "interface", "struct", "delegate", "enum"]}, "uniqueItems": true}
stylecop.schema.json
layoutRules
Configuration for layout rules (SA1500-)
{"type": "object", "additionalProperties": false, "properties": {"newlineAtEndOfFile": {"type": "string", "enum": ["allow", "require", "omit"], "default": "allow"}, "allowConsecutiveUsings": {"type": "boolean", "default": true}, "allowDoWhileOnClosingBrace": {"type": "boolean", "default": false}}}
stylecop.schema.json
newlineAtEndOfFile
Specifies the handling for newline characters which appear at the end of a file allow: Files are allowed to end with a single newline character, but it is not required require: Files are required to end with a single newline character omit: Files may not end with a newline character
{"type": "string", "enum": ["allow", "require", "omit"], "default": "allow"}
stylecop.schema.json
allowConsecutiveUsings
Specifies if SA1519 will allow consecutive using statements without braces
{"type": "boolean", "default": true}
stylecop.schema.json
allowDoWhileOnClosingBrace
Specifies if SA1500 will allow the 'while' expression of a 'do'/'while' loop to be on the same line as the closing brace.
{"type": "boolean", "default": false}
stylecop.schema.json
documentationRules
Configuration for documentation rules (SA1600-)
{"type": "object", "additionalProperties": false, "properties": {"documentExposedElements": {"type": "boolean", "default": true}, "documentInternalElements": {"type": "boolean", "default": true}, "documentPrivateElements": {"type": "boolean", "default": false}, "documentInterfaces": {"type": "boolean", "default": true}, "documentPrivateFields": {"type": "boolean", "default": false}, "companyName": {"type": "string", "default": "PlaceholderCompany"}, "copyrightText": {"type": "string", "default": "Copyright (c) {companyName}. All rights reserved."}, "variables": {"type": "object", "patternProperties": {"^[a-zA-Z0-9]+$": {"type": "string"}}, "additionalProperties": false}, "xmlHeader": {"type": "boolean", "default": true}, "headerDecoration": {"type": "string", "default": null}, "fileNamingConvention": {"type": "string", "default": "stylecop", "enum": ["stylecop", "metadata"]}, "documentationCulture": {"type": "string", "default": "en-US"}, "excludeFromPunctuationCheck": {"type": "array", "default": ["seealso"]}}}
stylecop.schema.json
documentExposedElements
Specifies whether exposed elements need to be documented. When true, all publicly-exposed types and members require documentation.
{"type": "boolean", "default": true}
stylecop.schema.json
documentInternalElements
Specifies whether internal elements need to be documented. When true, all internally-exposed types and members require documentation.
{"type": "boolean", "default": true}
stylecop.schema.json
documentPrivateElements
Specifies whether private elements need to be documented. When true, all types and members except for declared private fields require documentation.
{"type": "boolean", "default": false}
stylecop.schema.json
documentInterfaces
Specifies whether interface members need to be documented. When true, all interface members require documentation, regardless of accessibility.
{"type": "boolean", "default": true}
stylecop.schema.json
documentPrivateFields
Specifies whether private fields need to be documented. When true, all fields require documentation, regardless of accessibility.
{"type": "boolean", "default": false}
stylecop.schema.json
companyName
The name of the company which appears in file headers.
{"type": "string", "default": "PlaceholderCompany"}
stylecop.schema.json
copyrightText
The copyright text which should appear in file headers.
{"type": "string", "default": "Copyright (c) {companyName}. All rights reserved."}
stylecop.schema.json
variables
Replacement variables which may be used in the 'copyrightText' value.
{"type": "object", "patternProperties": {"^[a-zA-Z0-9]+$": {"type": "string"}}, "additionalProperties": false}
stylecop.schema.json
xmlHeader
Determines whether the file header should be wrapped in the StyleCop-standard XML structure.
{"type": "boolean", "default": true}
stylecop.schema.json
headerDecoration
The text used as decoration for the copyright header comment.
{"type": "string", "default": null}
stylecop.schema.json
fileNamingConvention
Specifies the preferred naming convention for files. The default value "stylecop" uses the naming convention defined by StyleCop Classic, while "metadata" uses a file naming convention that matches the metadata names of types.
{"type": "string", "default": "stylecop", "enum": ["stylecop", "metadata"]}
stylecop.schema.json
documentationCulture
The culture that should be used for documentation comments.
{"type": "string", "default": "en-US"}
stylecop.schema.json
excludeFromPunctuationCheck
Specifies the top-level tags within XML documentation that will be excluded from punctuation analysis.
{"type": "array", "default": ["seealso"]}
hazelcast-config-5.3.json
properties
The "properties" mapping lets you add properties to some of the Hazelcast elements used to configure some of the Hazelcast modules. You can define the name and value of these properties. You can use "properties" for the following Hazelcast configuration elements: \n * discovery-strategy \n * map-store \n * queue-store \n * wan-replication \n * ssl \n * service \n * login-module \n * security-object \n * socket-interceptor
{"type": "object"}
hazelcast-config-5.3.json
cluster-name
Specifies the cluster name. It's sent as part of the client authentication message to Hazelcast member(s).
{"type": "string"}
hazelcast-config-5.3.json
client-labels
The 'client-labels' sequence lets you define labels in your Java client, similar to the way it can be done for the members. Through the client labels, you can assign special roles for your clients and use these roles to perform some actions specific to those client connections. You can also group your clients using the client labels. These client groups can be blacklisted in the Hazelcast Management Center so that they can be prevented from connecting to a cluster. See the related section in the Hazelcast Management Center Reference Manual for more information on this topic.
{"type": "array", "uniqueItems": true, "items": {"type": "string"}}
hazelcast-config-5.3.json
backup-ack-to-client-enabled
The 'backup-ack-to-client-enabled' element lets you enable/disable backups ack to client. This feature reduces number of hops and increase performance for smart clients. It is enabled by default for smart clients. This config has no effect for unisocket clients.
{"type": "boolean", "default": true}
hazelcast-config-5.3.json
hazelcast-client-failover
The Hazelcast client can configurations that the client is using to connect to a Hazelcast cluster in the case of a disconnect is listed under the "clients" array. You can list client configurations as many as you want.
{"type": "object", "additionalProperties": false, "properties": {"clients": {"type": "array", "minItems": 1, "items": {"type": "string"}}, "try-count": {"type": "integer", "minimum": 0, "default": 2147483647}}}
hazelcast-config-5.3.json
scripting-enabled
Set to true to allow scripting on the member, false to disallow.
{"type": "boolean", "default": false}
hazelcast-config-5.3.json
console-enabled
Set to true to allow console commands execution on the member, false to disallow.
{"type": "boolean", "default": false}
hazelcast-config-5.3.json
data-access-enabled
Set to true to allow Management Center access to contents of Hazelcast data structures (for instance map entries), false to disallow. Management Center can't access the data if at least one member has the data access disabled.
{"type": "boolean", "default": true}
hazelcast-config-5.3.json
NetworkJoin
This configuration lets you choose a discovery mechanism that Hazelcast will use to form a cluster. Hazelcast can find members by multicast, TCP/IP lists and by various discovery mechanisms provided by different cloud APIs.
{"type": "object", "additionalProperties": false, "properties": {"multicast": {"type": "object", "additionalProperties": false, "properties": {"enabled": {"type": "boolean", "default": true}, "loopback-mode-enabled": {"type": "boolean", "default": false}, "loopbackModeEnabled": {"type": "boolean", "default": false}, "multicast-group": {"type": "string", "default": "224.2.2.3"}, "multicast-port": {"type": "integer", "default": 54327}, "multicast-time-to-live": {"type": "integer", "minimum": 0, "maximum": 255, "default": 32}, "multicast-timeout-seconds": {"type": "integer", "default": 2}, "trusted-interfaces": {"type": "array", "items": {"type": "string"}}}}, "auto-detection": {}, "tcp-ip": {"type": "object", "additionalProperties": false, "properties": {"enabled": {"type": "boolean", "default": false}, "connection-timeout-seconds": {"type": "integer", "minimum": 0, "default": 5}, "required-member": {"type": "string"}, "member": {"type": "string"}, "members": {"type": "string"}, "member-list": {"type": "array", "items": {"type": "string"}}, "interface": {"type": "string"}}}, "aws": {}, "gcp": {}, "azure": {}, "kubernetes": {}, "eureka": {}, "discovery-strategies": {}}}
hazelcast-config-5.3.json
multicast
Set its "enabled" attribute to true for discovery by multicast. It has another attribute ("loopback-mode-enabled") which enables or disables the loopback mode in the multicast discovery mechanism.
{"type": "object", "additionalProperties": false, "properties": {"enabled": {"type": "boolean", "default": true}, "loopback-mode-enabled": {"type": "boolean", "default": false}, "loopbackModeEnabled": {"type": "boolean", "default": false}, "multicast-group": {"type": "string", "default": "224.2.2.3"}, "multicast-port": {"type": "integer", "default": 54327}, "multicast-time-to-live": {"type": "integer", "minimum": 0, "maximum": 255, "default": 32}, "multicast-timeout-seconds": {"type": "integer", "default": 2}, "trusted-interfaces": {"type": "array", "items": {"type": "string"}}}}
hazelcast-config-5.3.json
enabled
Specifies whether multicast discovery is enabled.
{"type": "boolean", "default": true}
hazelcast-config-5.3.json
loopback-mode-enabled
Specifies if the loopback mode is enabled for multicast discovery.
{"type": "boolean", "default": false}
hazelcast-config-5.3.json
loopbackModeEnabled
Alias for loopback-mode-enabled
{"type": "boolean", "default": false}
hazelcast-config-5.3.json
multicast-group
Specifies the multicast group IP address when you want to create clusters within the same network.
{"type": "string", "default": "224.2.2.3"}
hazelcast-config-5.3.json
multicast-port
Specifies the multicast socket port that the Hazelcast member listens to and sends discovery messages through.
{"type": "integer", "default": 54327}
hazelcast-config-5.3.json
multicast-time-to-live
Time-to-live value for multicast packets sent out to control the scope of multicasts.
{"type": "integer", "minimum": 0, "maximum": 255, "default": 32}
hazelcast-config-5.3.json
multicast-timeout-seconds
Only when the members are starting up, this timeout (in seconds) specifies the period during which a member waits for a multicast response from another node. For example, if you set it as 60 seconds, each node will wait for 60 seconds until a leader node is selected.
{"type": "integer", "default": 2}
hazelcast-config-5.3.json
trusted-interfaces
Includes IP addresses of trusted members. When a node wants to join to the cluster, its join request will be rejected if it is not a trusted member. You can give an IP addresses range using the wildcard (*) on the last digit of IP address (e.g. 192.168.1.* or 192.168.1.100-110).
{"type": "array", "items": {"type": "string"}}
hazelcast-config-5.3.json
enabled
Specifies whether the TCP/IP discovery is enabled or not.
{"type": "boolean", "default": false}
hazelcast-config-5.3.json
connection-timeout-seconds
The maximum amount of time Hazelcast is going to try to connect to a well known member before giving up. Setting it to a too low value could mean that a member is not able to connect to a cluster. Setting it to a too high value means that member startup could slow down because of longer timeouts (e.g. when a well known member is not up). Increasing this value is recommended if you have many IPs listed and the members cannot properly build up the cluster.
{"type": "integer", "minimum": 0, "default": 5}
hazelcast-config-5.3.json
required-member
IP address of the required member. Cluster will only be formed if the member with this IP address is found.
{"type": "string"}
hazelcast-config-5.3.json
member
IP address(es) of one or more well known members. Once members are connected to these well known ones, all member addresses will be communicated with each other. You can also give comma separated IP addresses using the "members" element or list the members with the "member" element under "member-list".
{"type": "string"}
hazelcast-config-5.3.json
members
Comma separated IP addresses of one or more well known members.
{"type": "string"}
hazelcast-config-5.3.json
member-list
Sequence of IP address(es) of one or more well known members.
{"type": "array", "items": {"type": "string"}}
hazelcast-config-5.3.json
interface
IP address(es) of one or more well known members.
{"type": "string"}
hazelcast-config-5.3.json
MemberAddressProvider
IMPORTANT\nThis configuration is not intended to provide addresses of other cluster members with which the Hazelcast instance will form a cluster. This is an SPI for advanced use in cases where the DefaultAddressPicker does not pick suitable addresses to bind to and publish to other cluster members. For instance, this could allow easier deployment in some cases when running on Docker, AWS or other cloud environments. That said, if you are just starting with Hazelcast, you will probably want to set the member addresses by using the tcp-ip or multicast configuration or adding a discovery strategy. Member address provider allows to plug in own strategy to customize:\n1. What address Hazelcast will bind to\n2. What address Hazelcast will advertise to other members on which they can bind to\nIn most environments you don't need to customize this and the default strategy will work just fine. However in some cloud environments the default strategy does not make the right choice and the member address provider delegates the process of address picking to external code.
{"type": "object", "additionalProperties": false, "properties": {"enabled": {"type": "boolean", "default": false}, "class-name": {"type": "string"}, "properties": {"type": "object"}}}
hazelcast-config-5.3.json
enabled
Specifies whether the member address provider SPI is enabled or not.
{"type": "boolean", "default": false}
hazelcast-config-5.3.json
class-name
The name of the class implementing the com.hazelcast.spi.MemberAddressProvider interface.
{"type": "string"}
hazelcast-config-5.3.json
properties
The properties that will be provided when constructing the provided MemberAddressProvider. Hazelcast will first try instantiating the provided class by invoking a constructor accepting a single java.util.Properties instance. In the case where there is no such constructor and there are also no properties defined by this configuration, Hazelcast will exceptionally try to use the no-arg constructor.
{"type": "object"}
hazelcast-config-5.3.json
Interfaces
You can define multiple interfaces. By default, it is disabled.
{"type": "object", "additionalProperties": false, "properties": {"enabled": {"type": "boolean", "default": false}, "interfaces": {"type": "array", "items": {"type": "string"}}}}
hazelcast-config-5.3.json
enabled
You need to set it to true to be able to use your defined interfaces.
{"type": "boolean", "default": false}
hazelcast-config-5.3.json
FailureDetector
A failure detector is responsible to determine if a member in the cluster is unreachable or crashed. Please refer to https://docs.hazelcast.org/docs/latest/manual/html-single/index.html#failure-detector-configuration for the failure detectors implemented by Hazelcast.
{"type": "object", "additionalProperties": false, "properties": {"icmp": {"type": "object", "additionalProperties": false, "properties": {"enabled": {"type": "boolean", "default": false}, "timeout-milliseconds": {"type": "integer", "minimum": 1, "default": 1000}, "fail-fast-on-startup": {"type": "boolean", "default": true}, "interval-milliseconds": {"type": "integer", "minimum": 1000, "default": 1000}, "max-attempts": {"type": "integer", "minimum": 0, "default": 2}, "parallel-mode": {"type": "boolean", "default": true}, "ttl": {"type": "integer", "minimum": 0, "default": 255}}}}}
hazelcast-config-5.3.json
icmp
ICMP can be used in addition to the other detectors. It operates at layer 3 and detects network and hardware issues more quickly.
{"type": "object", "additionalProperties": false, "properties": {"enabled": {"type": "boolean", "default": false}, "timeout-milliseconds": {"type": "integer", "minimum": 1, "default": 1000}, "fail-fast-on-startup": {"type": "boolean", "default": true}, "interval-milliseconds": {"type": "integer", "minimum": 1000, "default": 1000}, "max-attempts": {"type": "integer", "minimum": 0, "default": 2}, "parallel-mode": {"type": "boolean", "default": true}, "ttl": {"type": "integer", "minimum": 0, "default": 255}}}
hazelcast-config-5.3.json
timeout-milliseconds
Timeout in milliseconds before declaring a failed ping.
{"type": "integer", "minimum": 1, "default": 1000}
hazelcast-config-5.3.json
fail-fast-on-startup
Cluster Member will fail to start if it is unable to action an ICMP ping command when ICMP is enabled. Failure is usually due to OS level restrictions.
{"type": "boolean", "default": true}
hazelcast-config-5.3.json
interval-milliseconds
Time in milliseconds between each ICMP ping.
{"type": "integer", "minimum": 1000, "default": 1000}
hazelcast-config-5.3.json
max-attempts
Maximum number of consecutive failed attempts before declaring a member suspect.
{"type": "integer", "minimum": 0, "default": 2}
hazelcast-config-5.3.json
parallel-mode
Run ICMP detection in parallel with the Heartbeat failure detector.
{"type": "boolean", "default": true}
hazelcast-config-5.3.json
ttl
Maximum number of times the IP Datagram (ping) can be forwarded, in most cases all Hazelcast cluster members would be within one network switch/router therefore default of 0 is usually sufficient.
{"type": "integer", "minimum": 0, "default": 255}
hazelcast-config-5.3.json
AwsDiscovery
Please refer to https://github.com/hazelcast/hazelcast-aws/#configuration for the configuration details.
{"type": "object", "properties": {"enabled": {"type": "boolean", "default": false}}}
hazelcast-config-5.3.json
enabled
Specifies whether AWS discovery is enabled or not.
{"type": "boolean", "default": false}
hazelcast-config-5.3.json
GcpDiscovery
Please refer to https://github.com/hazelcast/hazelcast-gcp/#configuration for the configuration details.
{"type": "object", "properties": {"enabled": {"type": "boolean", "default": false}}}
hazelcast-config-5.3.json
enabled
Specifies whether Google Cloud Platform discovery is enabled or not.
{"type": "boolean", "default": false}
hazelcast-config-5.3.json
AzureDiscovery
Please refer to https://github.com/hazelcast/hazelcast-azure/#configuring-at-hazelcast-side for the configuration details.
{"type": "object", "properties": {"enabled": {"type": "boolean", "default": false}}}
hazelcast-config-5.3.json
enabled
Specifies whether Microsoft Azure discovery is enabled or not.
{"type": "boolean", "default": false}
hazelcast-config-5.3.json
KubernetesDiscovery
Please refer to https://github.com/hazelcast/hazelcast-azure/#configuring-at-hazelcast-side for the configuration details.
{"type": "object", "properties": {"enabled": {"type": "boolean", "default": false}}}
hazelcast-config-5.3.json
enabled
Specifies whether Microsoft Azure discovery is enabled or not.
{"type": "boolean", "default": false}
hazelcast-config-5.3.json
EurekaDiscovery
Please refer to https://github.com/hazelcast/hazelcast-eureka#hazelcast-configuration for the configuration details.
{"type": "object", "properties": {"enabled": {"type": "boolean", "default": false}}}
hazelcast-config-5.3.json
enabled
Specifies whether Eureka Service Registry discovery is enabled or not.
{"type": "boolean", "default": false}
hazelcast-config-5.3.json
items
Set its "enabled" sub-element to true for discovery in various cloud infrastructures. You also need to set the value of "hazelcast.discovery.enabled" property to true. See the description of the "properties" element to learn how to do this. You can define multiple discovery strategies using the "discovery-strategy" sub-element and its properties. Please refer to http://docs.hazelcast.org/docs/latest/manual/html-single/index.html#discovering-cluster-members to see the properties you can use.
{"type": "object", "additionalProperties": false, "properties": {"enabled": {"type": "boolean", "default": true}, "class": {"type": "string"}, "properties": {"type": "object"}}}
hazelcast-config-5.3.json
public-address
Overrides the public address of a node. By default, a node selects its socket address as its public address. But behind a network address translation (NAT), two endpoints (nodes) may not be able to see/access each other. If both nodes set their public addresses to their defined addresses on NAT, then they can communicate with each other. In this case, their public addresses are not an address of a local network interface but a virtual address defined by NAT. This is optional to set and useful when you have a private cloud.
{"type": "string"}
hazelcast-config-5.3.json
reuse-address
When you shutdown a cluster member, the server socket port will be in the TIME_WAIT state for the next couple of minutes. If you start the member right after shutting it down, you may not be able to bind it to the same port because it is in the TIME_WAIT state. If you set reuse-address to true, the TIME_WAIT state is ignored and you can bind the member to the same port again.
{"type": "boolean", "default": false}
hazelcast-config-5.3.json
port
Specifies the ports that Hazelcast will use to communicate between cluster members.
{"type": "object", "additionalProperties": false, "properties": {"port": {"type": "integer", "minimum": 0, "maximum": 65536, "default": 5701}, "port-count": {"type": "integer", "default": 100, "minimum": 1}, "auto-increment": {"type": "boolean", "default": true}}}
hazelcast-config-5.3.json
port-count
By default, Hazelcast will try 100 ports to bind (i.e. the ports between 5701 and 5801). You can change the port count in such cases as having large instances on a single machine or you are willing to have only a few ports assigned.
{"type": "integer", "default": 100, "minimum": 1}
hazelcast-config-5.3.json
auto-increment
By default, Hazelcast tries to find a port by automatically incrementing the port numbers. If you don't want this (for example, you want to use a specific port), set auto-increment to false. If it is set to false, the port-count attribute is ignored.
{"type": "boolean", "default": true}
hazelcast-config-5.3.json
memcache-protocol
Allows to configure Memcache text protocol support in Hazelcast.
{"type": "object", "additionalProperties": false, "properties": {"enabled": {"type": "boolean", "default": false}}}
hazelcast-config-5.3.json
symmetric-encryption
Lets you encrypt the entire socket level communication among all Hazelcast members. This feature is available only in Hazelcast Enterprise. Its configuration contains the encryption properties and the same configuration must be placed to all members. By default, it is disabled.
{"type": "object", "additionalProperties": false, "properties": {"enabled": {"type": "boolean", "default": false}, "algorithm": {"type": "string", "default": "PBEWithMD5AndDES"}, "password": {"type": "string"}, "salt": {"type": "string"}, "iteration-count": {"type": "integer", "default": 19}}}
hazelcast-config-5.3.json
enabled
Indicates whether the advanced network configuration is enabled or not.
{"type": "boolean", "default": false}
hazelcast-config-5.3.json
wan-server-socket-endpoint-config
Configures the server sockets used for the WAN replication's inbound WAN connections. Multiple WAN server sockets can be configured to allow configuring separate server sockets for each inbound WAN connection.
{}
hazelcast-config-5.3.json
client-server-socket-endpoint-config
Configures the server socket used for the member-client communication.
{}
hazelcast-config-5.3.json
member-server-socket-endpoint-config
Configures the server socket used for the member-member communication.
{}
hazelcast-config-5.3.json
wan-endpoint-config
This element configures socket settings for the outgoing WAN connections.
{"type": "object", "additionalProperties": {}}
hazelcast-config-5.3.json
rest-server-socket-endpoint-config
Controls access to Hazelcast HTTP REST API. The methods available through REST API are grouped to several REST endpoint groups, which can be specified in this section.
{"allOf": [{}, {"properties": {"endpoint-groups": {}}, "propertyNames": {"enum": ["endpoint-groups", "port", "public-address", "reuse-address", "name", "outbound-ports", "interfaces", "ssl", "socket-interceptor", "symmetric-encryption", "socket-options", "tpc-socket"]}}]}
hazelcast-config-5.3.json
split-brain-protection-ref
Adds the Split Brain Protection for this data-structure which you configure using the "split-brain-protection" element. You should set the "split-brain-protection-ref"'s value as the "split-brain-protection"'s name.
{"type": "string"}
hazelcast-config-5.3.json
InMemoryFormat
Binary type that will be used for storing records. Possible values: BINARY (default): keys and values will be stored as binary data. OBJECT: values will be stored in their object forms. NATIVE: values will be stored in non-heap region of JVM (Hazelcast Enterprise only)
{"enum": ["BINARY", "OBJECT", "NATIVE"], "default": "BINARY"}
hazelcast-config-5.3.json
unique-key-transformation
Defines an assortment of transformations which can be applied to unique-key values. OBJECT: Extracted unique key value is interpreted as an object value. Non-negative unique ID is assigned to every distinct object value. LONG: Extracted unique key value is interpreted as a whole integer value of byte, short, int or long type. The extracted value is upcasted to long (if necessary) and unique non-negative ID is assigned to every distinct value. RAW: Extracted unique key value is interpreted as a whole integer value of byte, short, int or long type. The extracted value is upcasted to long (if necessary) and the resulting value is used directly as an ID.
{"enum": ["OBJECT", "LONG", "RAW"], "default": "OBJECT"}
hazelcast-config-5.3.json
page-size
Page size of the index B+ Tree. Default value is 16 kB.
{"default": {"value": 16, "unit": "KILOBYTES"}}
hazelcast-config-5.3.json
memory-tier
Memory tier.
{"type": "object", "additionalProperties": false, "properties": {"capacity": {}}, "default": {"capacity": {"default": {"value": 16, "unit": "KILOBYTES"}}}}
hazelcast-config-5.3.json
capacity
Memory tier capacity, i.e., how much main memory should this tier consume at most. The default is 256 megabytes.
{}