Apache Doris
Operate Apache Doris through your OOMOL-connected account. This skill calls the doris connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.
Running an action
Assume the user has already installed the oo CLI, signed in, and connected Apache Doris. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.
1. Inspect the contract to get the authoritative input/output schema before building a payload:
oo connector schema "doris" --action "<action_name>"
2. Run the action with a JSON payload that matches the input schema:
oo connector run "doris" --action "<action_name>" --data '<json>' --json
--datatakes a JSON object string or@path/to/file.json; omit it to send{}.- The response is
{ "data": ..., "meta": { "executionId": "..." } }; the execution id lives undermeta.executionId.
Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.
Available actions
execute_query— Run one read-only SELECT, WITH, SHOW, DESC, DESCRIBE, or EXPLAIN statement against Apache Doris. Writes, INTO OUTFILE, SQL hints, and multiple statements are rejected. Responses are capped at 8 MiB.get_table_schema— Describe a Doris table. Result rows describe fields, types, nullability, keys, defaults, and extra attributes. Set database here or on the connection.list_databases— List databases visible to the connected Doris user. Each result row contains a database name.list_tables— List tables and views in a Doris database. Set database here or on the connection.
Safety
- Untagged actions are reads (get / list / search) — safe to run directly.
- Actions tagged
[write]change Apache Doris state — confirm the exact payload and effect with the user before running. - Actions tagged
[destructive]remove or overwrite data — always confirm the target and get explicit approval first.
First-time setup
These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.
oo: command not found— install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linuxirm https://cli.oomol.com/install.ps1 | iex # Windows PowerShellNot signed in / authentication error — sign in to your OOMOL account once:
oo auth loginscope_missing/credential_expired/app_not_ready/app_not_found— Apache Doris is not connected, or the connection expired or lacks a scope. Connect once (auth type: custom credential) at:https://console.oomol.com/connections/dorisOOMOL_INSUFFICIENT_CREDIT— OOMOL billing stop. Recharge athttps://console.oomol.com/billing/token-rechargebefore retrying.HTTP 402 without
OOMOL_INSUFFICIENT_CREDIT— the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.
Resources
- Apache Doris homepage: https://doris.apache.org
- API documentation: https://doris.apache.org/docs/dev/admin-manual/open-api/fe-http/statement-execution-action/