extracted from our tracker sample which is available here: https://github.com/apache/unomi/blob/master/extensions/web- tracker/wab/src/main/webapp/index.html . However you will still need to use the ships with a set of predefined JSON Schemas, detailed here: https://github.com/apache/unomi/tree/master/extensions/json- schema/services/src/main/resources/META-INF/cxs/schemas. "unevaluatedProperties": we provide an example of such a rule. You can find it here: https://github.com/apache/unomi/blob/master/samples/login-integration/src/main/resources/META- INF/cxs/rules/exampleLogin.json As you can see

you can configure like so for master and also for the slave: <master> 12 master> When a backup loses connection to the master it will keep voting for a quorum until it either receives a vote allowing it to start or it detects that the master is still live. for the latter it will then <master> true 2 master>

you can configure like so for master and also for the slave: <master> 12 master> When a backup loses connection to the master it will keep voting for a quorum until it either receives a vote allowing it to start or it detects that the master is still live. for the latter it will <master> true 2 master>

you can configure like so for master and also for the slave: <master> 12 master> When a backup loses connection to the master it will keep voting for a quorum until it either receives a vote allowing it to start or it detects that the master is still live. for the latter it will <master> true 2 master>

you can configure like so for master and also for the slave: <master> 12 master> When a backup loses connection to the master it will keep voting for a quorum until it either receives a vote allowing it to start or it detects that the master is still live. for the latter it will <master> true 2 master>

you can configure like so for master and also for the slave: <master> 12 master> When a backup loses connection to the master it will keep voting for a quorum until it either receives a vote allowing it to start or it detects that the master is still live. for the latter it will <master> true 2 master>

you can configure like so for master and also for the slave: <master> 12 master> When a backup loses connection to the master it will keep voting for a quorum until it either receives a vote allowing it to start or it detects that the master is still live. for the latter it will <master> true 2 master>

you can configure like so for master and also for the slave: <master> 12 master> When a backup loses connection to the master it will keep voting for a quorum until it either receives a vote allowing it to start or it detects that the master is still live. for the latter it will <master> true 2 master>

you can configure like so for master and also for the slave: <master> 12 master> When a backup loses connection to the master it will keep voting for a quorum until it either receives a vote allowing it to start or it detects that the master is still live. for the latter it will <master> true 2 master>

you can configure like so for master and also for the slave: <master> 12 master> When a backup loses connection to the master it will keep voting for a quorum until it either receives a vote allowing it to start or it detects that the master is still live. for the latter it will <master> true 2 master>