From 585688fe60084cc65ae6ccca1279d5d21878e804 Mon Sep 17 00:00:00 2001 From: Kris Zyp Date: Thu, 31 Oct 2024 08:52:53 -0600 Subject: [PATCH] Drop database/table can be replicated --- docs/developers/operations-api/databases-and-tables.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/developers/operations-api/databases-and-tables.md b/docs/developers/operations-api/databases-and-tables.md index 2816806..1f2fc27 100644 --- a/docs/developers/operations-api/databases-and-tables.md +++ b/docs/developers/operations-api/databases-and-tables.md @@ -187,6 +187,7 @@ _Operation is restricted to super_user roles only_ * operation _(required)_ - this should always be `drop_database` * database _(required)_ - name of the database you are dropping +* replicated _(optional)_ - if true, HarperDB will replicate the component to all nodes in the cluster. Must be a boolean. ### Body ```json @@ -248,6 +249,7 @@ _Operation is restricted to super_user roles only_ * operation _(required)_ - this should always be `drop_table` * database _(optional)_ - database where the table you are dropping lives. The default is `data` * table _(required)_ - name of the table you are dropping +* replicated _(optional)_ - if true, HarperDB will replicate the component to all nodes in the cluster. Must be a boolean. ### Body