Browse and edit ClickHouse data

Browse databases and tables, read with cost checks, and edit rows only when ClickHouse can identify them, or change by filter.

The sidebar lists databases, tables, views, materialized views and dictionaries. System databases are hidden until you ask for them. Columns that are ALIAS, MATERIALIZED or EPHEMERAL carry a badge that explains what they are. A table’s engine, sort key and partition key are shown, because they decide what reads and writes can do.

The data grid reads in pages and can filter by column. Reads past 100,000 rows are refused, so you filter or export instead. Without a stable sort, Tablyne warns that pages may repeat or skip rows. Sorting by a column outside the sort key and reading with FINAL both show the estimated parts and rows and ask you to confirm. An exact count is a separate button and can be cancelled.

Tablyne edits a row only when ClickHouse can pin it down. Three cases work:

  • Lightweight. A MergeTree table with block number and offset columns. If the table lacks them, Tablyne offers to turn them on with a reviewed ALTER TABLE … MODIFY SETTING, which costs about 3% of disk.
  • By version. A ReplacingMergeTree with a version column. Each edit writes the next version. Concurrent edits can overwrite each other, and the review says so.
  • Insert only. Some tables accept new rows but not edits.

The grid refuses to write in some cases and sends nothing. A table without a UUID, which means an Ordinary or Lazy database, is one. A table with a projection, a replicated table on your own cluster and a view are others. The reason is shown next to the grid. Lightweight UPDATE is Beta on some server versions, and the app says so.

For everything else there is “Change by filter”. It prepares a lightweight delete, an ALTER … DELETE or an ALTER … UPDATE for every row that matches the filter. The result is a mutation that finishes later. You can follow it in the Mutations tab and request an interrupt, which does not undo what has already changed.