dodil k3 engine

You usually don’t need these commands. Every bucket gets an auto-enabled table engine on CreateBucket — dodil k3 engine enable runs implicitly. This page is for advanced scenarios: applying custom settings after the fact, disabling tables on a bucket without dropping it, or troubleshooting.

The engine is the per-bucket backend configuration. One engine per bucket; all tables in the bucket share it. See Core Concepts → Engine.

Persistent flag on the group: --bucket / -b (required).

dodil k3 engine enable

dodil k3 engine enable -b BUCKET

Most callers never run this — CreateBucket enables the engine implicitly. Use it to re-enable an engine you previously disabled.

dodil k3 engine enable --bucket kb-prod

Custom settings (the settings JSON-string field on the API) aren’t exposed as CLI flags today. For custom settings, use the API directly — see API Reference → EnableEngine.

dodil k3 engine get

dodil k3 engine get -b BUCKET

Returns the engine row — status, table count, settings, timestamps.

dodil k3 engine get --bucket kb-prod -o json

Sample output (pbjson):

{
  "engineId": "eng_a1b2…",
  "bucket": "kb-prod",
  "status": "ENGINE_STATUS_ACTIVE",
  "settings": "{}",
  "tableCount": 4,
  "createdAt": "1716840000000",
  "updatedAt": "1716843600000"
}

Useful for confirming the engine is ACTIVE (the default from CreateBucket) and seeing how many tables it’s hosting.

dodil k3 engine disable

dodil k3 engine disable -b BUCKET

Disables the engine for the bucket. Does not delete tables — table rows + Delta data remain intact — but blocks new writes / reads against any of them.

dodil k3 engine disable --bucket kb-prod
# `dodil k3 engine get` now returns status = ENGINE_STATUS_DISABLED
# Re-enable with `dodil k3 engine enable` to resume Table operations.

Disable is reversible — enable flips it back. The engine row + engineId + tableCount persist; only status changes.

See also

• Engine — API Reference — full surface incl. custom settings
• Core Concepts → Engine — type + status enum
• dodil k3 table — lifecycle — what to do once the engine is on (which is always, by default)