2026.09.79 — 2026-09-30

Breaking

• Move Remove cluster from the cluster header to its settings (b6b12906)

  Removing a cluster is now the last section of the cluster's settings, under This cluster → Remove cluster, instead of a button in the header shown above every view of the cluster. The section lists what Studio deletes (its registration, nodes, credentials, alert rules, request-reply flows, message-index subscriptions and configuration history) and what stays (the broker and its messages, and the audit trail) before the typed cluster name arms the button. A failed removal now says why and that the cluster is still registered; a successful one returns to the start page.

Added

• Move Remove cluster from the cluster header to its settings (b6b12906)

  Removing a cluster is now the last section of the cluster's settings, under This cluster → Remove cluster, instead of a button in the header shown above every view of the cluster. The section lists what Studio deletes (its registration, nodes, credentials, alert rules, request-reply flows, message-index subscriptions and configuration history) and what stays (the broker and its messages, and the audit trail) before the typed cluster name arms the button. A failed removal now says why and that the cluster is still registered; a successful one returns to the start page.

• Browse a JSON body as a tree and copy a field's SQL path (cc220f2a)

  The message view's Formatted / Raw switch gains Tree for a JSON body: objects and arrays collapse and expand, a filter finds keys and values and opens the path to each match, and selecting a field shows the path the SQL console takes for it (body->>'order.lines.0.sku') with a Copy path button.

  A body the broker held compressed is labelled with it, e.g. JSON · gzip.

  Download of a binary body now saves its bytes (.bin) instead of the base64 text that carried it.

• Search text carried in bytes messages in the message index (f4ce50b9)

  The message index now stores a bytes message whose body is text as that text, so MATCH word and phrase search and body->>'path' find it like any other message. Only a genuinely binary body is left out of full-text search. The message detail reports the compression a body was unwrapped from (bodyCompression: gzip or deflate).

  A JSON path now steps into arrays by index (body->>'lines.0.sku') against the live broker too, as it already did over the index.

  Sampled index rows now record whether the broker truncated their body, as captured rows already did, so a body predicate over a cut body warns instead of silently missing.

  Rows indexed before this release keep their stored form and age out with retention; no step is needed.

• Read text carried in a bytes message as text (503cf3ea)

  A bytes message whose body is UTF-8 text, such as JSON or XML sent through a BytesMessage, is now read as text wherever Studio reads it from the broker, over Core and over Jolokia. The message view, the queue's body column, the SQL console, the message index and request-reply payloads show the text instead of a hex dump or base64. The message type still reads bytes.

  A gzip- or zlib-compressed body is decompressed when the result is text, up to 2 MiB; past that, or when it is not text, it stays binary. Real binary bodies are unchanged. Moving, copying and relaying messages still carry the original bytes.

  Over Jolokia, a bytes body is read from the broker's body preview. A preview cut at the address's management-message-attribute-size-limit is reported as truncated, with the same notice as a truncated text body.