Read-only is Druid here, not the integration
Update and delete are not in this SQL anywhere, create is not in the grammar, and the refusals are surfaced word for word instead of rewritten.
5 posts
Writing on Apache Druid
SQL over HTTP with datasource and segment introspection for streaming analytics. Where it stops: Append-oriented: row editing is disabled rather than offered and then failed.
Druid has no query sessions, so the panel shows tasks
Rows come from the task table and every column is relabelled to say so, because there is no session catalog and no query log anywhere to read.
Connecting to Apache Druid on the Router or the Broker
Both ports serve the identical SQL endpoint and nothing in the connection knows which it reached, and there is no database field because there is one catalog.
A Druid plan tree with no cost anywhere on it
The plan returns the native query the cluster will run, rendered in its own operator vocabulary, and the planner publishes no cost and no row estimate.
A missing Druid datasource is an availability question first
Marking segments unused removes a datasource from the catalog entirely, and a stopped node makes an existing one answer with the same error as a typo.