Change Log
Contains a history of changes made to the Agent.
https://console.warpstream.com/agent-changelog.rssChange Log
Release v840
September 10, 2026
Tableflow:
Breaking change: Rename
warpstream.tableflow_partition_offset_lagtowarpstream.tableflow_ingestion_offset_lag. Tableflow cluster lag metrics now omit tags listed in-tableflowClusterMetricsTagDenyList/WARPSTREAM_TABLEFLOW_CLUSTER_METRICS_TAG_DENY_LIST. Valid values aretable,topic, andpartition(defaults topartition). An empty value emits all tags.tabledrops both thetable_nameandtable_uuidtags.
Bump Apache Thrift to v0.24.0, the RabbitMQ AMQP 0.9.1 client to v1.14.0, and gRPC to v1.83.2 to address CVE-2026-43871, CVE-2026-79921, and SNYK-GOLANG-GOOGLEGOLANGORGGRPCINTERNALTRANSPORT-19651825.
Support path-prefix wildcards in SPIFFE mTLS ACL principals, e.g.
User:spiffe://acme.com/team/*now authorizes any workload under that path. Previously only the whole-trust-domain wildcardUser:spiffe://acme.com/*was supported.Rework the
alter-topic-configandalter-broker-configCLI sub-commands to support incremental alter config. They now take kafka-configs style--add-config "k1=v1,k2=v2"and--delete-config "k1,k2"flags and default toIncrementalAlterConfigs, so only the specified configs are changed. Pass--full-stateto replace the entire config set via the legacyAlterConfigsAPI. Breaking: the old single-pair--config-name/--config-valueflags are removed, and thedelete-broker-configsub-command is removed in favor ofalter-broker-config --delete-config.
Release v839
September 8, 2026
Tableflow:
Add telemetry to detect orphaned snapshot files.
Update the Lakehouse runtime catalog integration to automatically infer namespace locations for multi-bucket catalogs.
Fix a bug where the metadata.json files created automatically by the Lakehouse runtime catalog were being orphaned.
Bump build to go
1.27.1Fix CVE-2026-56855
Report object storage lifecycle policies that can corrupt your Warpstream clusters and buckets whose policies cannot be verified. Agents now require
s3:GetLifecycleConfigurationfor S3,s3express:GetLifecycleConfigurationfor S3 Express, andstorage.buckets.getfor GCS to inspect lifecycle configurations (https://docs.warpstream.com/warpstream/agent-setup/different-object-stores).Add a
diagnostic_agent_grouplabel towarpstream.diagnostic_failure. Agent-pushed diagnostics emit one series per live and recently departed agent group. Diagnostics without an applicable or known reporting group usediagnostic_agent_group="no_group". Usemax by (diagnostic_name)to monitor overall cluster health andsum by (diagnostic_name)to count failing agent groups per diagnostic.
Release v838
September 4, 2026
Change the default max concurrent files for each fetch to 64.
Refresh negatively cached schema validation lookups (schema_not_found) after 1 minute.
Release v837
September 4, 2026
Set CGv2 request UUID from the Agent.
Update the consumer group analyzer for modern consumer groups.
Change the default max concurrent files for each fetch to 64.
Fix query engine queries timing out on mTLS-authenticated clusters with ACLs enabled.
Release v836
August 31, 2026
Reduce Agent memory and garbage collection overhead used to remember per-connection Metadata partition assignments. Large clusters no longer keep a full Go map of every topic-partition per Kafka connection.
Fix misleading ACL shadow-denial logs for
CreateTopics. A CLUSTER CREATE miss is no longer logged as[shadow_acl:not_enforced]when the request is allowed by a topic-level CREATE ACL (for example Kafka Connect creating its internal topics).
Release v835
August 27, 2026
Fix Metadata v1+ treating a non-null empty topic list as "return all topics". That now matches Apache Kafka: null (or empty on v0) returns every topic; an empty list on v1+ returns brokers only. Metadata error responses follow the same rule and no longer inject a synthetic error topic for empty v1+ lists. This could cause very high CPU and egress on clusters with many clients.
Add
agent_kafka_request_received_bytesandagent_kafka_request_transmitted_bytescounters, tagged bykafka_key, for Kafka protocol bytes received from and written to clients.Add a
workspace_idlabel to hosted Prometheus cluster metrics, Agent-published metrics, andcluster_metricsevents.
Release v834
August 26, 2026
Enable multi-source Orbit.
Upgrade Bento to v1.21.1.
Tableflow: Fixes a bug where we stopped reporting lag on DLQ topics when they were fully caught up.
Bump agent base image (
cgr.dev/chainguard/wolfi-base) to fixCVE-2026-38754,CVE-2026-38753,CVE-2026-38752(busybox) andCVE-2026-54876(libcrypto3/libssl3).Fix
orbit_source_cluster_offsetsconsumer group lag reporting a false spike for a fully-migrated Orbit topic whose destination partition had aged out via retention.Add
agent_group_overridesto Orbit pipeline configs, letting agents in different-agentGroups reach the source cluster via different bootstrap brokers.
Release v833
August 21, 2026
Make sure that agent metrics include the
virtual_cluster_nametag when possible.Tableflow: deletion file rewrites now stream output Parquet row groups instead of buffering the entire output file in memory until close.
Release v832
August 19, 2026
Tableflow:
Add the ability to create more row groups per Parquet file for ingestion.
Relax ingestion file size constraint.
Add the following metrics:
The
agent_tableflow_parquet_file_num_rowsdistribution metric tracks the number of rows per Parquet file.The
agent_tableflow_ingestion_live_partitionsgauge tracks the number of distinct Iceberg partitions created during ingestion.
Prevent deleted source topics from blocking Orbit fetches for healthy topics.
Stop paging the file-cache invariant
single actor stream returned N bytes, but M were requestedwhen the Fetch is already canceled. A canceled request could close the stream while it was still being copied, which looked like a short stream.warpstream local: add-saslUser,-superUsers, and-enableACLsso integration tests can start a local cluster with named SASL users and Kafka ACL enforcement. Also fix-requireSASLAuthenticationstoring/printing the password asREDACTED.Fix a bug in the HTTP fetch endpoints where the pooled fetch buffers were returned to the buffer pool before the HTTP response encoder had finished reading them (the JSON response references the buffers zero-copy). Under concurrent load, another fetch could re-lease the buffers and overwrite them mid-encode, corrupting the HTTP fetch response. The buffers are now only released after the response has been fully encoded and written.
Bump build to Go 1.26.6 and
golang.org/x/modto v0.40.0 to fix CVE-2026-39821, CVE-2026-46600, CVE-2026-33818, CVE-2026-56853, CVE-2026-56862, CVE-2026-56859, CVE-2026-56864, and CVE-2026-56865.Add
blob_store_write_durationmetric, tagged bybucket_url, reporting per-sub-bucket write latency for striped buckets.
Release v831
August 14, 2026
Tableflow:
Add the
WARPSTREAM_TABLEFLOW_ASSUME_ROLE_ARNand optionalWARPSTREAM_TABLEFLOW_ASSUME_ROLE_DURATION_MINUTESenvironment variables for a shared STS AssumeRole used by both S3 bucket access and AWS Glue catalog sync. When set, the Tableflow role supersedesWARPSTREAM_BUCKET_ASSUME_ROLE_*for bucket access.Fix a bug where the bucket URL
prefixquery parameter wasn't being respected when AssumeRole is used.
Stop logging an error when setting or clearing a connection's read deadline fails because the connection was already closed. This just means the client disconnected.
Add the
loading_queue_used_count,loading_queue_discard_count, andloading_queue_load_outcome(tagged byoutcome) metrics, all tagged byqueue(prepared_upload,jobs, orfile_id), so it's possible to see how many items each of the agent's loading queues handed out, aged out unused, and failed to load.
Release v830
August 13, 2026
Tableflow:
A
schemacan now be defined inline in schema registry mode and will be used as the schema used to write records in Parquet files. This is handy for defining transforms that change of the shape of the data being inserted into the table.
The
error handling connection, closing itlog now includes theclient_idof the Kafka client that was using the connection.Remove noisy log when the context is canceled for speculative reads.
The auto migration forwarded produce metrics
warpstream.agent_kafka_produce_forwarded_records_counter,warpstream.agent_kafka_produce_forwarded_compressed_bytes_counterandwarpstream.agent_kafka_produce_forwarded_compressed_bytesare now tagged byoutcome, so records that the source Kafka cluster rejected are reported alongside the ones it accepted. Possible values aresuccess,error, andunverified(used when producing withacks=0, where the source cluster sends no response and the Agent cannot confirm the records were accepted).
Release v829
August 12, 2026
Tableflow:
Add the
-tableflowHighCardinalityDistributionMetricsflag (WARPSTREAM_TABLEFLOW_HIGH_CARDINALITY_DISTRIBUTION_METRICSenvironment variable) to control whether high cardinality per table distribution metrics are emitted. Defaults to false.
Fix pure-Go
Lz4BlockCompressAppendso it appends to the destination prefix instead of discarding it, which could corrupt Kafka record-batch headers written before compression.Fix flexible Kafka response framing so reused connection write buffers always emit an empty response-header tagged-fields count. A stale byte (for example after SASL handshake v0) could make clients fail to decode later flexible responses such as Fetch.
Fix a race that could assign the same Kafka connection ID to an external connection and an in-process direct-dialer connection, and refuse to serve a prefetched Fetch response when the claimer's Fetch API version does not match the originator's.
Fix noisy "async gcs rapid storage writer close failed" logs with
context canceledduring Rapid Storage uploads by decoupling the writer context from caller cancelation while preserving the deadline.The
metricssubcommand now supports OIDC workload identity federation via the-workloadIdentityTokenSourceflag (andWARPSTREAM_AGENT_WORKLOAD_IDENTITY_TOKEN_SOURCEenvironment variable), matching theagentsubcommand. When set,-enableControlPlanePrometheusEndpointis forced totruebecause the exchanged agent token is only accepted by the control plane's prometheus endpoint.Enable public Agent releases to receive control-plane-generated Events on Kafka clusters, including diagnostics and Orbit migration events.
Size the batcher's prepared upload queue and load concurrency off the agent's CPU quota instead of the host's CPU count, so containerized agents no longer over-create prepared upload files.
Stop deleting prepared upload files that lose the race for a spot in the batcher's queue. They now wait for the next free spot, which removes the object store create and delete each one used to cost.
Release v828
August 10, 2026
Tableflow:
Add the
agent_tableflow_parquet_file_size_uncompressedandagent_tableflow_parquet_file_size_compresseddistribution metrics for Parquet files, tagged bysource(ingestion,compaction, ordeletion).Add the
agent_tableflow_parquet_file_num_row_groups,agent_tableflow_row_group_size_uncompressed, andagent_tableflow_row_group_size_compresseddistribution metrics for Parquet row groups, tagged bysource(ingestion,compaction, ordeletion).Add support for multi-bucket catalogs in BigLake.
Add experimental support for upsert tables (
table_type: upsert): records are deduplicated by Kafka record key within each source partition (highest offset wins) and records with null values delete the key from the table.
Fetch requests that include an unknown or invalid topic ID (for example, a recently deleted topic referenced by TopicID only) now return a partition-level error for that topic instead of failing the entire Fetch. Valid topics in the same request continue to return data, matching Apache Kafka behavior.
Release v827
August 4, 2026
Add diagnostic to detect when the Orbit auto migration client has connectivity issues with the source cluster.
Fix incorrect
failed to lookup AZ from CIDR mappingwarnings for the Agent's own internal clients (like the query engine).Improve auto migration's logic to detect if a produce request is transactional by actually checking if the record batch has the transactional flag in its attributes.
Upgrade Bento to v1.20.0.
Add the user-provided
credential_nameto ACL denial logs.warpstream local: allow clients to use session / rebalance / transaction timeouts below the normal broker minimums so unit tests against local can run faster (previously rejected).Skip shadow ACL denial noise for in-process direct-dialer clients (e.g. the agent's query engine / events UI).
Accept OAuth bearer tokens on the HTTP Fetch and Produce APIs. When
saslOauthIssuerURLandsaslOauthAudienceare configured, HTTP clients can authenticate withAuthorization: Bearer <token>in addition to HTTP Basic auth; bearer tokens are validated via the same OAUTHBEARER path used by the Kafka wire protocol.Migrate direct imports from
github.com/hamba/avro/v2togithub.com/iskorotkov/avro/v2v2.33.1to addressCVE-2026-46384,CVE-2026-46385, andGHSA-mx64-mj3q-7prj. Transitivehamba/avrousage remains until dependent modules move off it.Set
MaxMapAllocSizeon Tableflow Avro decode of untrusted Kafka payloads to mitigate map-allocation DoS (GHSA-mx64-mj3q-7prj).Added bucket striping (
warpstream_stripe://$URL_1<>$URL_2<>...<>$URL_N, 2–32 sub-buckets): an object-storage wrapper that scales writes past a single bucket's request-rate ceiling by striping objects across sub-buckets. Placement is deterministic — each object lives on exactly one sub-bucket, chosen by hashing its key. Writes fail over to another sub-bucket when the target's circuit breaker is open; reads go to the hashed sub-bucket and fall back to the others on NotFound. Unlikewarpstream_multi://(which replicates for read availability), striping stores each object once, so a sub-bucket outage makes its objects unreadable — the same blast radius as a single bucket. Retiring a sub-bucket by shortening the URL strands dead files on it unless the retired bucket (or the previous stripe URL) is added toadditionalBackgroundTasksBucketURLs.
Release v826
July 29, 2026
Tableflow:
Introduce a maximum uncompressed row size limit for Tableflow ingestion, measured after projection and transforms. Records that exceed the limit are handled based on the configured DLQ policy.
Use a more precise memory measurement for Tableflow ingestion buffering.
Added new metric
warpstream_orbit_auto_migration_unproxied_source_writes_num_records: counts the number of detected unproxied records to the source cluster that bypassed the WarpStream proxy.tags:
topic=<topic>
Add
agent_groupto root metric tags so metrics likewarpstream.agent_kafka_request_latencyandwarpstream_consumer_group_lagare groupable by agent group in Datadog.Fix SASL OAUTHBEARER rejecting non-RS256 tokens (e.g. ES512) when the OAuth 2.x authorization server is discovered via RFC 8414 and does not advertise
id_token_signing_alg_values_supported.Fix events queries returning an internal error instead of a "no events data found" message when an event topic was created moments earlier and the stream metadata cache had not caught up yet.
Adds support for auto-migrating idempotent producers via Orbit.
Release v825
July 24, 2026
Add Confluent REST Proxy v2-compatible and multi-topic HTTP produce endpoints.
Tableflow: Fix ingestion trying to flush an empty file (
failed to add record to buffer: failed to sort and flush: cannot flush empty record batch).Bump
google.golang.org/grpctov1.82.1to fixGHSA-hrxh-6v49-42gf.
Release v824
July 22, 2026
Managed Data Pipelines: when the number of pipelines Agents changes, scale pipeline instance concurrency up or down instead of stopping and restarting all pipelines.
Fix a throughput bottleneck during Orbit auto-migration
PROXY.
Release v823
July 21, 2026
Fixes a panic that impacted the
democommand, theplaygroundcommand, and agents connected to a Tableflow cluster (panic: failed to initialize duckdb client dependencies).OAUTHBEARER SASL: fall back to
/.well-known/oauth-authorization-server(RFC 8414) when OpenID Connect discovery at/.well-known/openid-configurationfails, so identity providers that only implement the RFC 8414 discovery endpoint can be used.Tableflow: Add support for custom table names. When a table is renamed, the tagging of logs for that table will start to use the new name.
Release v822
July 20, 2026
Tableflow:
Reject decimal values that exceed the column type's declared precision with an error instead of panicking during ingestion.
Release sorting and column statistics tracking for Iceberg decimal types.
Fix false-positive "Cannot Access Tableflow Schema Registry" health diagnostic against WarpStream BYOC Schema Registry (and other registries that do not implement
GET /mode).
Remove the legacy AWS SDK v1 from agent binaries to prevent false-positive CVE-2020-8911 reports.
GCS Rapid Storage: flush on close instead of waiting for a full synchronous Close, reducing write finalize latency.
Add a
delete-broker-configCLI sub-command (warpstream cli delete-broker-config --config-name <name>) that resets a broker config to its default viaIncrementalAlterConfigswith a delete op.
Release v821
July 14, 2026
Tableflow:
Store decimals with precision greater than 18 as FIXED_LEN_BYTE_ARRAY in Parquet.
Add a health diagnostic that checks connectivity to schema registry integrations.
Upgrade Bento for the
parse_big_decimalbloblang method (Kafka Connect / Debezium decimal decoding).OIDC workload identity federation now works on multi-region clusters (and across single-region cluster migrations): the agent holds a short-lived token per region and presents the one minted by whichever region it is talking to.
Promote
warpstream cli-betatowarpstream cli— it is now the default Kafka CLI.warpstream cli-betastill works as a deprecated alias (prints a deprecation warning on stderr) and will be removed in a future release. The previouswarpstream clicommand has been renamed towarpstream cli-oldand will be retired eventually;warpstream kcmdcontinues to work as before. Note: this is potentially a breaking change since some commands are different and most of the flags are different.
Release v820
July 10, 2026
Tableflow:
Add Schema Registry integration for Avro schemas.
Enable LZ4 compression in benchmkark-producer CLI command and tweak defaults to be more sane.
Fix a data race when speculative object storage uploads finish concurrently.
Release v819
July 10, 2026
Tableflow:
Emit diagnostic and event when the subject is not found in the Schema Registry.
Upgrade Bento to v1.19.0 (requires Go 1.26.5).
Bump build to go
1.26.5.
Release v818
July 9, 2026
Added a new
warpstream localcommand that runs a fully in-memory, self-contained WarpStream cluster (Kafka + Schema Registry + Tableflow) with no connection to the WarpStream control plane. Intended as a replacement forwarpstream playgroundin CI pipelines.Automatically run
warpstream localwhenwarpstream demoorwarpstream playgroundis started in CI, with a warning that local mode is designed for CI environments.Agent: dynamically tune the direct load prefetch concurrency based on observed CPU usage instead of using a fixed value of 16. Underloaded agents can still serve up to 64MiB of concurrent prefetch per request, but as CPU usage rises the concurrency automatically steps down to avoid the agent DDOSing itself with prefetch work it can't transmit in time, which previously caused wasted GET requests and slow recovery under high load.
Orbit: add support for JSON key/value secrets in Cloud Provider's Secrets Manager. A secret reference in the Orbit config can now specify an optional
keyto extract a single value from a secret stored as a JSON object (the standard AWS Secrets Manager key/value pattern). AWS secrets stored as binary (SecretBinary) are now supported as well.Ensure
Close()is called on the pooled buffer after all replicas complete on the quorum-success path of multi-bucketPutBytes.Add cluster-level default partition auto scaler settings (
warpstream.default.partitions_auto_scaler.*broker configs) that are applied to newly created topics, so a cluster can enable partition auto scaling by default for all new topics.
Release v817
July 8, 2026
Tableflow:
Expose Schema Registry writer schema ID and version as
warpstream.sr.writer_schema_idandwarpstream.sr.writer_schema_versionto ingested records before applying Bento transforms so that the transform logic can condition on those properties.Make BigLake integration automatically detect catalogs with credential vending mode and send
X-Iceberg-Access-Delegationheader on Iceberg REST calls if so.
Release v816
July 6, 2026
Allow Orbit to chunk requests when copying consumer group offsets.
Schema Registry: include Confluent-compatible
guidvalues in schema API responses and support looking up schemas by GUID withGET /schemas/guids/{guid}.
Release v815
July 2, 2026
Add support of
-disableConsumerGroupMetrics(env varWARPSTREAM_DISABLE_CONSUMER_GROUP_METRICS) and-disableConsumerGroupsMetricsTags(env varWARPSTREAM_DISABLE_CONSUMER_GROUP_METRICS_TAGS) in agentmetricsmode to offer the same knobs as in regular agent mode over cluster level metrics cardinality. By default-disableConsumerGroupsMetricsTagsis set to empty string (the default value for regular agents ispartition).Tableflow:
Add support for OAuth as an authentication mechanism for source Kafka clusters.
Fix Go runtime CPU utilization reporting so stale high samples decay when the Go runtime has not emitted a fresh CPU metrics snapshot.
Auto enable bucket pre-warming when the bucket is of type Rapid Storage.
Reduce default value of GOGC for Agents running only pipelines role from 1000 to 200.
Release v814
July 1, 2026
Fixed a bug in the Prometheus metrics scraping path where the
warpstream_max_offsetandwarpstream_min_offsetmetrics were summed across partitions instead of taking the max/min when thepartitiontag is disabled.Fix the metric double publishing problem introduced in
v808when the dedicated metrics mode was enabled (the regular agents would keep publishing the same metrics).Improve produce latency for GCP Rapid Buckets by pre-warming upload streams.
Add a new
-additionalBackgroundTasksBucketURLsflag andWARPSTREAM_ADDITIONAL_BACKGROUND_TASKS_BUCKET_URLSenvironment variable that accepts a comma-separated list of bucket URLs that should have background tasks run on them like scanning for dead files to delete or ripcord files to ingest. This is important for customers who are migrating from one bucket to another. The new flag supersedes the existing-additionalDeadscannerBucketURLsflag andWARPSTREAM_ADDITIONAL_DEADSCANNER_BUCKET_URLSenvironment variable.Add support for OIDC workload identity federation: when
WARPSTREAM_AGENT_WORKLOAD_IDENTITY_TOKEN_SOURCEis set, the agent obtains a platform OIDC token and exchanges it with the control plane for a short-lived agent token, removing the need for a static agent key. Currentlyaws(STS) andgcp(metadata server) sources are supported, but other platforms may be added in the future. Supported for single-region clusters only.Add an opt-in file ID allocator (behind the
use_range_file_id_allocatorflag, default off) that hands out IDs from several discontiguous reserved ranges to spread object-storage key prefixes more evenly and reduce metadata-layer hot-spotting. The key layout is unchanged. TheWARPSTREAM_USE_RANGE_FILE_ID_ALLOCATORenvironment variable (true/false) is the final per-Agent override for the flag.
Release v813
June 29, 2026
Tableflow:
Update internal compaction API usage.
Fix bug where the schema registry integration feature was not ungated properly.
Add support of Cloud Provider's Secrets Manager in TableFlow config.
Add a new flag
-skipBucketsPermissionCheck(env varWARPSTREAM_SKIP_BUCKETS_PERMISSION_CHECK) that allows to skip the permission check for buckets when starting an agent. The default value is false.Improve DNS resolution of S3 addresses by automatically injecting a
.at the end of any S3 endpoint we try to connect to. This is a workaround because the AWS SDK does not support it to this day https://github.com/aws/aws-sdk-go/issues/1380.Re-enable GCS direct connectivity client by default.
Disable some connection-level backpressure mechanisms when TLS is enabled because once we've paid the price of accepting a TLS connection and doing the formal handshake, paradoxically, backpressuring that connection by closing it due to high load makes the situation worse as the client will just try to re-establish the connection and the TLS handshake is extremely expensive.
Stop playground agents from logging query engine state refresh errors when query engine credentials are not required.
Release v812
June 22, 2026
Move orbit consumer offset copying job entirely into the agents.
Release v811
June 22, 2026
Tableflow:
Add Schema Registry integration for Protobuf schemas.
Fix Tableflow ingestion getting stuck (
no ranges were processed, possibly due to timeout) on source topics written by transactional producers (e.g. CDC), where the offset at the high watermark is a transaction control marker that a read-committed consumer never receives.
Add support of Cloud Provider's Secrets Manager in Orbit config.
Schema Registry: prevent an incompatible type change of a
oneoffield when that field'soneofblock is renamed or dissolved. This matches a bug fix in Confluent's protobuf compatibility that will be released in Confluent Platform 8.3.1.
Release v810
June 19, 2026
Tableflow:
Support sorting and column statistics on
floatanddoublecolumns.
Schema Registry: Match Confluent's protobuf compatibility behavior by allowing a type change on a
oneoffield is now allowed when that field'soneofblock is renamed or dissolved.
Release v809
June 18, 2026
Orbit now creates empty source topics with a non-zero log end offset at that offset in WarpStream. This fixes a bug where an empty source topic could be migrated to WarpStream at offset 0 instead of preserving its source log end offset.
Add a
cli-beta validate-pipeline-configcommand for validating managed data pipeline config files locally. Usage:warpstream cli-beta validate-pipeline-config --config-file pipeline.yaml.Restrict which clients see support for KIP-714 client metrics APIs. The GetTelemetrySubscriptions and PushTelemetry endpoints will no longer be advertised to clients older than this version.
Release v808
June 18, 2026
Tableflow:
Add support for sorting and column statistics tracking for Iceberg tables.
Fix time-based partition transform on an Avro date field.
Update the publish metrics job implementation to scrape metrics from the control plane Prometheus endpoint. This should not change any of the existing metric, but will add a few that were only available in the control plane Prometheus endpoint.
Release v807
June 12, 2026
Orbit Auto Migration is now available.
Release v806
June 12, 2026
Forward produce backpressure metrics for observability.
Add support for OAuth as an authentication mechanism for source clusters in Orbit.
Tableflow: Validate properly the required fields nested under untyped maps via
additionalPropertiesfor JSON ingestion.Bump agent base image (
cgr.dev/chainguard/wolfi-base) to pick up busybox fix forCVE-2023-39810.
Release v805
June 10, 2026
KIP-714 client metrics are now generally available to all customers.
Release v804
June 9, 2026
Add global sort duration in batcher to flush_end log.
Fix a bug where the agent could have problems listing ripcord files if there were too many of them and your bucket URL was long, because the generated output was too big.
Fix Orbit and Tableflow source connections silently dropping SASL when TLS is enabled without mTLS.
Release v803
June 8, 2026
Warning: This version drops SASL when connecting to an Orbit or Tableflow source cluster over TLS without mTLS. It is fixed in v804. Please upgrade to v804 directly and skip v803.
Fix panic when emitting the client availability zone mismatch diagnostic during interzone load balancing.
Upgrade Bento to v1.18.1.
Fix Orbit and Tableflow source cluster TLS configuration to allow setting a private CA (
mtls_server_ca_cert_env) without requiring mTLS.Schema Registry: the
error_codefor incompatible schema responses now returns40901(was409) to align with Confluent's documented API. The HTTP status code remains409.Schema Registry: Avro schemas with invalid field defaults are now rejected at registration time (aligns with Confluent SR 8.2.1 behavior). Existing schemas registered before this change are unaffected.
Add batching for JoinGroup and SyncGroup requests via RSM batch commands, reducing the number of RSM proposals when many consumers join/sync concurrently.
Release v802
June 4, 2026
Bump build to go
1.26.4to fixCVE-2026-42504Add an agent flag to override max inflight fetch compressed bytes per CPU.
Upgrade Bento to v1.18.0
Tableflow:
Fix bug for
dlq_keep_settings.retention: we now allow fordandwunits for days and weeks respectively.Fix bug that considered null values set within transforms as non-null when fields were marked as required.
Tableflow agents can now create Iceberg table metadata even when they cannot access external blob store buckets directly. This can be enabled by setting the
tableflowMetadataSyncModeflag toproxy.Support converting between booleans and strings, and between integers and strings, in both directions when mapping records to the destination schema.
Breaking Change (AWS Glue): Fix a bug in the AWS Glue integration that caused us to hit the TableVersions limit when syncing the table. This fixes the error
Number of TABLE_VERSION resources exceeds the limit 100000 per TABLE. Note that agents will now require additional roles:glue:GetTableVersionsandglue:BatchDeleteTableVersion.Fix some tags on the event emitted when sending records to the DLQ.
Release v801
May 29, 2026
Deprecate a legacy code path for computing Data Lake sorting bounds and column statistics.
Fix events scheduler writing a corrupt active state when an event type was disabled while events were globally enabled. Agents now drop records with stream ID 0 instead of poisoning the file batch.
Tableflow: Implement basic validation for required / nullable fields in JSON.
Release v800
May 27, 2026
Tableflow:
Fix bug on transforms: Bento transforms replacing the full root object instead of modifying it field by field are now handled correctly (e.g.
root = { ...}now works).
Fix
warpstream_consumer_group_estimated_lag_very_coarse_do_not_use_to_measure_e2e_secondsreporting full retention as the lag for partitions with no committed offset. The metric now uses the age of the oldest surviving record (bounded by retention).
Release v799
May 27, 2026
Fix events queries failing with
UNSUPPORTED_SASL_MECHANISMon clusters that restrictenabledSASLMechanismsto excludePLAIN.
Release v798
May 26, 2026
Fix a query engine bug that could cause Agent panics for some sorted and limited queries.
Fix false positive diagnostic for cross az traffic when the query engine was used.
Fix false positive diagnostic for small fetch timeout when the query engine was used.
Return clear error when schema registry request body size exceeds limit.
Release v797
May 19, 2026
Tableflow:
Fix decoding of Protobuf
oneoffields (introduced in v796, upgrade directly to v797 if you use a configuration with Protobuf schemas).Recreate BigLake tables when the Iceberg table UUID changes.
Fix DNS-backed Agent file cache retries so failed replicas can fall back to other resolved Agents.
Add per-pipeline log level controls for managed data pipelines.
Fix event queries on agents with SASL enabled.
Release v796
May 18, 2026
Warning: There is a problem for Tableflow protobuf schemas with that version fixed in v797. Please upgrade to v797 directly and skip v796 if you use Tableflow with a protobuf schema.
Upgrade the embedded version of Bento to v1.17.0.
Start supporting regional migrations.
Add a rate limiter in the metrics mode to throttle metrics emission. This avoids flooding the Datadog agent when Datadog metrics are enabled.
Adds an experimental agent flag that can be used to reduce E2E latency for workloads that do not produce new records consistently on all partitions all the time.
Tableflow:
Breaking change for very old agent versions using protobuf, they would need to upgrade to version 796+.
Add support for field type remapping
Release v795
May 14, 2026
Forward schema registry metrics for observability.
Tableflow: Fix the Tableflow configuration used in the demo mode.
Reduced telemetry sent from Agents to control plane.
Release v794
May 12, 2026
Add a diagnostic for invalid regex subscriptions in modern consumer group heartbeat requests.
Bump
golang.org/x/nettov0.54.0to fixCVE-2026-33814Detect when Kafka clients request one availability zone via
ws_azbut produce or fetch against an Agent in a different availability zone and fire a diagnostic.
Release v793
May 11, 2026
Unless customers specify a
-metadataURL/WARPSTREAM_METADATA_URLthe agents will start using 3 different "zonal" endpoints to communicate with WarpStream - meaning one per WarpStream control plane availability zone. The previous behavior can be put back by setting the environment variableWARPSTREAM_AGENT_ENABLE_ZONAL_URLSto false. Removes a dependency on inconsistent behavior across cloud providers when load balancing across multiple availability zones and increases the product's resiliency to zonal outages significantly.Bump build to go
1.26.3Fixed CVEs: CVE-2026-39820 / CVE-2026-33811 / CVE-2026-42499 / CVE-2026-39820 / CVE-2026-33811 / CVE-2026-39836
Agent will now enforce read-only Schema Registry credentials and only allow read schema operations for read-only credentials.
Release v792
May 8, 2026
Add optional PROXY protocol v2 support on the Kafka listener via
kafkaProxyProtocol(orWARPSTREAM_KAFKA_PROXY_PROTOCOL). When enabled, every connection must include a v2 PROXY header before any other bytes; v1 headers are rejected. Operators can also setkafkaProxyProtocolPrincipalTLVType(a hex byte in the PP2 user-defined range0xE0–0xEF) to source the connection's ACL principal from a custom TLV in the PROXY header — the TLV value must already include theUser:prefix and overrides any principal that would otherwise be derived from mTLS.Tableflow:
Fix a bug in ingestion that was not respecting some types from the input schema.
Fix ingestion of date types for Avro input schemas.
Fix ingestion of Avro map types with optional values when the deprecated way of specifying schemas is used.
Fix several correctness bugs in the Protobuf decoder so records now align with the proto3 spec (
oneoflast-wins, merging of repeated singular message fields, strict wire-type validation).
Release v791
May 6, 2026
Fix a bug in the agent metrics mode that would cause it to stall when any of the metrics scraped contained a comma in its labels.
Mark file cache closed-pipe logs as debug.
Release v790
May 5, 2026
Tableflow: Make ingestion handle partition evolution.
Bump our Chainguard Wolfi Docker image to
79af0917ba7ac066ebf1f99e5967ee9e77e6a350facec5be43a7a236c705cf10to fixCVE-2026-5450andCVE-2026-5928.Fix a bug in the query engine when querying across events that mix integers and floats in the same field name.
Fix a bug in the query when combining multiple filters like: filter a=="b" | filter c=="d" where only the latter filter would be applied.
Release v789
April 30, 2026
Fix a bug where object store errors due to networking issues (DNS or TCP timeouts, context cancellation, etc) were misclassified as NotFound errors, causing red-herring invariant violations.
Tableflow: Fix ingestion of list types with optional elements.
Public agent docker images and release tarballs now ship
notices.txt(auto-generated from the binary's transitive Go dependencies) andnon_ibm_license.txtat the container/archive root, for IBM third-party legal compliance.Fix the reason for a decision made during compaction in a log from being wrong.
Treat "unexpected EOF" as a retriable error for long-running compactions.
Release v788
April 29, 2026
Bump
github.com/aws/smithy-gotov1.25.1. This fixes a very slow memory leak associated with using S3 Express One Zone in the AWS SDK.
Release v787
April 28, 2026
Query engine: disable the admin RPC metadata cache because it causes a bug with inconsistent results when querying events.
Query engine: fix
::int,::float, and::strcasts in event queries, and make integer/float comparisons work in filters.Agents will now automatically backpressure Kafka protocol requests when their CPU is >= 98% for a sustained period of time. This threshold can be adjusted by setting the
WARPSTREAM_HIGH_CPU_BACKPRESSURE_THRESHOLD_PERCENTenvironment variable and disabled by setting it to 0.All Datadog metrics now include
virtual_cluster_id,agent_id, andagent_versiontags.
Release v786
April 28, 2026
Emit cluster-level Prometheus-style metrics (consumer group lag, topic details, diagnostics, tableflow state, ...) as
cluster_metricsCloudEvents whenever events are enabled on the cluster. Emission is independent of the Datadog push: events are still emitted even whenDisableAllMetricsorDisableConsumerGroupMetricsis set. Events are always at topic-level granularity (partition tag is always stripped) to keep the per-job event volume bounded. The event'smetric_namefield carries the canonicalwarpstream_-prefixed name (e.g.warpstream_consumer_group_lag), identical to the Prometheus scrape name and thedescribe_cluster_metricsAPI response, so the same string identifies a metric regardless of how it is queried.Tableflow: improve DLQ health reporting so records routed to the DLQ are no longer surfaced as skipped, reducing misleading health warnings and making it clearer when data was retained for later replay.
Improve query engine performance by caching metadata lookups and aligning query time boundaries.
Move modern consumer group heartbeat regex matching and topic
DESCRIBEACL filtering from saasy into the agent, and forward the resolved regex stream IDs to saasy for statemachine application.Allow reserved keywords like topic to parse as part of .-deleted field identifiers in the query engine.
Release v785
April 23, 2026
Emit cluster-level Prometheus-style metrics (consumer group lag, topic details, diagnostics, tableflow state, ...) as
cluster_metricsCloudEvents whenever events are enabled on the cluster. Emission is independent of the Datadog push: events are still emitted even whenDisableAllMetricsorDisableConsumerGroupMetricsis set. Events are always at topic-level granularity (partition tag is always stripped) to keep the per-job event volume bounded.Make metrics pod use external HTTP client to have longer connect timeouts.
Make metrics pod re-use HTTP client across requests to reduce time spent on establishing new connections.
Change
consoleURLparameter name toapiURL.Fix a bug that would cause the original error to be dropped from error messages and logs when hedging requests with the fast retrier.
Fix bug in query parser for handling sub expressions.
Make tableflow events all have the table name and table UUID fields set properly.
Fix panic in query engine related to nested expression and or statement.
Emit a tableflow event when the offset scraper job handler fails.
Enable the agent query engine by default and require
disableQueryEngineto opt out of query handling.Removed the
OBJECT_STORAGE_PUBLIC_NETWORK_PATHdiagnostic (added in v765).Added a diagnostic that fires when a produce request contains records for both lightning and classic topics, which removes the latency benefit of the lightning topic.
Release v784
April 20, 2026
Fix a memory leak when using the
metricsagent mode.Bump
github.com/aws/aws-sdk-go-v2/aws/protocol/eventstreamtov1.7.8,github.com/aws/aws-sdk-go-v2/service/kinesistov1.43.5,github.com/aws/aws-sdk-go-v2/service/lambdatov1.89.0andgithub.com/aws/aws-sdk-go-v2/service/s3tov1.99.0to fixGHSA-xmrv-pmrh-hhx2.WarpStream Agents will no longer report the availability zone that they're running in as the value of the Rack field in Broker metadata in the response of Metadata RPCs. Instead, they will always report their Rack as: "warpstream-fake-rack". The reason for this is that WarpStream's service discovery system tracks availability zones of clients using client ID features, not this Rack field. In addition, when clients enable rack-awareness for consumers in their Kafka clients without properly configuring WarpStream's zone-aware service discovery system, the presence of the availability zone in the Rack field in the Broker's metadata, combined with the fact that it will change from time to time due to how WarpStream's partition assignment strategies work, may result in an excessive number of consumer group rebalances. As a result, since this field has no value in WarpStream clusters, we're hard-coding the value of Rack so that misconfigured clients will not experience excessive consumer group rebalances.
Tableflow:
Fix ingestion of Avro fixed and time types.
Performance improvement when sorting is enabled on tables.
Release v783
April 16, 2026
Tableflow:
Reject invalid combinations of
WARPSTREAM_BUCKET_URL,WARPSTREAM_INGESTION_BUCKET_URLandWARPSTREAM_COMPACTION_BUCKET_URLwith an explicit error message for datalake agents with events enabled.
Bump
go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttptov1.43.0forCVE-2026-39882vulnerability.Fix connection reuse on the query engine.
Fix a bug that didn't allow users to manually disable events for tableflow clusters.
Release v782
April 14, 2026
Tableflow: add
warpstream.tableflow_dlq_records_counteragent metric tagged bytopicandstrategy(skiporkeep) to track records handled by the DLQ during ingestion. Replaces the previouswarpstream.ingestion_job_dlq_skip_strategy_counterwhich only covered the skip strategy.Improve query engine performance by fixing connection reuse.
Improve produce latency by parallelizing record sorting in the agent batcher hot path.
Fix Avro schema validation to handle references using short name within a namespace properly.
Bump
go.opentelemetry.io/otel/sdktov1.43.0forCVE-2026-39883vulnerability.Improve how runtime CPU measurements are taken to be more precise and not persist inaccurate values for long period of time by occasion.
Improved agent feature versioning scheme to auto-compute latest released version from feature declarations, eliminating manual maintenance and potential for version bump errors
Query engine: fix distributed aggregation for aliased
count()andcount(expr)so merge/final stages consume the correct intermediate count columns.CLI
alter-broker-confignow surfaces per-broker error responses instead of silently reporting success.Support setting
warpstream.default.topic.typevia AlterConfigs and IncrementalAlterConfigs.Unknown warpstream-prefixed broker and topic configs now return an error instead of being silently ignored.
Release v781
April 9, 2026
Breaking Change (GCP): WarpStream Agents now depend on
storage.buckets.getaccess for all configured GCP (gcs://) bucket URLs. This can be overriden by setting the environment variableWARPSTREAM_GCS_PERFORM_BUCKET_STORAGE_CLASS_LOOKUP=false.Allow configuring the
tracerblock in managed data pipeline configs.Automatically disable idempotent writes for managed data pipelines writing to WarpStream clusters via
kafka_franz_warpstreamoutput blocks.Fix non-determinism in generating schema hash for unrecognized key in Avro schemas.
Bump build to go
1.26.2Add support for GCP Rapid Buckets.
Optimize metrics code, particularly when emitting Datadog metrics.
Fix the docker image base to properly use the multi-arch wolfi-base image
Release v780
April 8, 2026
Reduce max diagnostic groups per type from 10 to 5 to lower payload size sent to the control plane.
Remove spammy error log when diagnostic groups exceed the per-type limit.
Forward sampled flush_event logs for observability.
Emit forwarded flush synchronous duration metric.
Bump our Chainguard Wolfi Docker image to
79af0917ba7ac066ebf1f99e5967ee9e77e6a350facec5be43a7a236c705cf10to fixCVE-2026-4437.Bump
github.com/go-jose/go-jose/v4tov4.1.4to fixGHSA-78h2-9frx-2jm8.Prevent a single fetch request from triggering thousands of concurrent HTTP requests if it's querying data for many topic-partitions whose individual data is spread across many files.
Install CURL in Agent image so it can be used in health checks for services like ECS that rely on container having command line utilities available.
Tableflow: tableflow events are generally available and agent-side events handling is enabled by default. This is a breaking change since tableflow agents now require a bucket URL to be configured (either
WARPSTREAM_BUCKET_URLor bothWARPSTREAM_INGESTION_BUCKET_URLandWARPSTREAM_COMPACTION_BUCKET_URL). Agents without bucket URLs will fail to start.Enable events when bootstrapping demo and playground clusters.
Added SLOW_CONSUMER push diagnostic: detects consumers that are too slow between fetch requests using a dynamic threshold (baseline + 1s per MB of previous response size) and emits the diagnostic after 3 consecutive slow fetches on a connection.
Fix GOMEMLIMIT parsing to support byte suffixes like "24GiB" and "1000MB" instead of requiring plain integers.
Fix GOGC, GOMAXPROCS, and GOMEMLIMIT heartbeat reporting to not report a value on parse error. Previously a parse error would silently report 0.
Release v779
April 1, 2026
Fix bug that prevented query engine from running queries successfully on Agents configured to only run the Jobs role.
Release v778
April 1, 2026
Add principal impersonation via record headers. Configured impersonator principals can produce messages on behalf of other users by setting a designated record header, enabling ACL evaluation as the impersonated principal.
Fix a bug that caused events queries to fail on agents with mTLS enabled.
Enable dual-mode Prometheus native histograms alongside classic histograms for improved metric accuracy.
Query engine: route query jobs only to agents with the query engine enabled and fail fast if an agent is configured to accept only query jobs without enabling the query engine.
Replace mutex-protected
rand.Randinstances with lock-free top-levelrandfunctions in certain hot paths.Fix a bug that was preventing events from being emitted/enabled in public Agent builds.
Enable agent-side events handling and query engine automatically for Kafka agents.
Expose a
/debug/pprof/traceendpoint for Go runtime tracesTableflow: fix a bug where compaction failed on certain parquet file layouts with gaps between column chunks, leaving small files unmerged.
Tableflow: add
type: "record_ingestion_failed"to logs corresponding to decoding errors during ingestion.Tableflow: add
warpstream.tableflow_ingestion_lag_secondsandwarpstream.tableflow_query_lag_secondsmetrics. Ingestion lag measures how far behind the ingestion process is from the source Kafka topic. Query lag measures the time from when data is produced to Kafka until it is queryable (ingestion lag + catalog sync delay).
Release v777
March 26, 2026
Fix schema validation in playground by passing missing schema registry URL to config.
Release v776
March 26, 2026
Tableflow:
Add
warpstream.tableflow_partition_offset_laggauge for Tableflow ingestion offset lag in records. When topic or partition tags are omitted, offset lag is summed across partitions (likeconsumer_group_lag); time lag remains the max per scope.
Release v775
March 25, 2026
Add topic, partition, and streamID to orbit offset error messages for easier debugging.
Release v774
March 25, 2026
Cache metrics in fetch and produce Kafka handlers to reduce tagset allocations when updating metrics.
Tableflow:
Fix panic in demo mode by adding missing
input_schemato demo config.
Add topic tag to
agent_kafka_produce_with_offset_uncompressed_bytes_countermetric when high cardinality metrics are enabled.
Release v773
March 24, 2026
Don't swallow circuit breaker errors and make it clear in error logs that are showing cached circuit breaker errors what is happening.
For instance consumers could start failing when some Kafka topics are deleted but are still trying to be accessed, because the metadata response would be incorrect
Don't count structured errors from the control plane (400s) as failures in the control plane client circuit breakers.
Release v772
March 23, 2026
Fixed IPv6 address parsing.
Tableflow:
Make the
TABLEFLOW_prefix optional for environment variables used to specify Kafka cluster credentials.Fix BigQuery integration for Tableflow tables failing to update when the Iceberg schema evolves (e.g., new columns added).
Add support for ConsumerGroupDescribe API (key 69, KIP-848) for the modern consumer group protocol. Disabled by default.
Make the
ORBITprefix optional for environment variables used to specify Kafka cluster credentials.Fix the
empty_responsetag value for thewarpstream.agent_kafka_fetch_single_attempt_outcomemetric.Bump
google.golang.org/grpctov1.79.3forCVE-2026-33186vulnerability.Bump our Chainguard Wolfi Docker image to
ce84795834de56c47f27b6be64388628677d18e799e9b5a05fe6538aaa17bc79to fixCVE-2026-2673.Upgrade Bento to
v1.16.1to get Datadog and Bigtable outputs support.Query engine: stop clamping query tail offsets from cached stream metadata so Event Explorer queries do not intermittently miss recent time buckets.
Add Datadog-compatible HTTP log intake endpoints on Agents so Datadog log batches can be routed into WarpStream topics.
Add a zstd produce fallback decoder path so Agents can accept some batches that fail
github.com/DataDog/zstdwithunexpected EOFbut succeed withklauspost/compress/zstd.
Release v771
March 19, 2026
Fix the metrics prefix pushed by the agent in
metricsmode: in previous versions we would add back a "warpstream_" prefix to all metrics, which was redundant.
Release v770
March 18, 2026
Fix: re-include
ncin the warpstream-agent image so that healthchecks can be performed properly on ECS.
Release v769
March 18, 2026
Tableflow:
Add BigLake Metastore integration via Iceberg REST Catalog API for GCP data lake tables.
Add Hive Metadata Store integration
Release v768
March 12, 2026
Disable GCS direct connectivity client by default as it is causing a regression in some GCP regions.
Release v767
March 11, 2026
Fix
tls_insecure_skip_verifynot being applied for TLS+SASL connections without mTLS in Tableflow and Orbit source clusters.Prevent Agents from trying to issue file cache requests against Agents that no longer exist when fetching old file extents by enforcing a maximum cache staleness in the activation cache.
Release v766
March 11, 2026
Bump build to go
1.26.1Tableflow:
Enhance logging when metadata upload fails.
Add a
moduleattribute to job logs to group them logically.Fix the command to query the Tableflow table logged by the demo agent.
Fail agent startup if the ripcord mode is used for an agent connecting to a Tableflow or a Schema Registry cluster.
Add observability by forwarding agent produce error outcomes.
Switch agent Docker base images from Alpine to Chainguard Wolfi https://images.chainguard.dev/directory/image/wolfi-base/overview
Misc: New way of releasing static agent features, this should be a transparent change.
Add
create-acls,describe-acls, anddelete-aclsclibeta commands for managing ACLs from the CLI, providing akafka-acls.shequivalent.
Release v765
March 5, 2026
Tableflow: Add retries to the bucket access checker and remove extra slash used in the request URL.
Add
agent_versionlabel/tag to all metrics emitted by the agents.Bump
github.com/docker/clitov29.2.1forCVE-2025-15558vulnerability.Add L7 proxy detection diagnostic for inter-agent traffic. When a load balancer or reverse proxy is detected between agents, a new high-severity diagnostic is surfaced to help users identify and remove proxy interference.
Added new
OBJECT_STORAGE_PUBLIC_NETWORK_PATHdiagnostic that detects when S3 or Azure Blob Storage endpoints resolve to public IPs, indicating a missing VPC endpoint (or equivalent). This helps identify unnecessary networking costs from object storage traffic going over the public internet.Fix a bug where some log attributes were grouped into a
!BADKEYkey.
Release v764
March 3, 2026
Tableflow: make Protobuf type
google.protobuf.Timestampusable as a custom partitioning field.
Release v763
February 27, 2026
Increase the maximum allowed value for
batchMaxSizeBytes(max uncompressed batch flush size) from 64MiB to 128MiB.Improve Schema Registry to properly handle trailing slashes in URL paths (e.g.,
/config/now works the same as/config).
Release v762 [do not use]
February 26, 2026
Make sure BYOC schema registry response's Content-Type is application/json if the request's Accept header is application/json.
Fixed a bug where the demo agent would get stuck waiting for the Tableflow Iceberg table to be created.
Optimizes fetch to use less CPU and IO when fetching a single record, or when
max.partition.fetch.bytesis low.
Release v761
February 25, 2026
Add PSI (Pressure Stall Information) metrics collection for CPU, memory, and I/O pressure. New metrics:
pressure_cpu_some_pct,pressure_cpu_full_pct,pressure_memory_some_pct,pressure_memory_full_pct,pressure_io_some_pct,pressure_io_full_pct. These metrics report the percentage of time tasks were stalled due to resource contention over the last sampling interval (0-100%).Update orbit to cover for protocol incompatibility in some systems which implement kafka api
Release v760
February 24, 2026
Tableflow: Performance improvement on ingestion saving 5 to 10% of CPU usage.
Add
metricscategory to--jobSelectorflag, allowing agents to run only metrics publishing jobs (e.g.,--jobSelector metrics).
Release v759
February 24, 2026
Add
--jobSelectorflag (env:WARPSTREAM_JOB_SELECTOR) to specify which job types an agent handles.
Release v758
February 20, 2026
Tableflow:
Fix ingestion of Avro and JSON when lists or map values contain decimal fields.
Make Proto unsigned integers (
uint32,uint64,fixed32,fixed64) convert into decimals. Before that, making a Protobuf backward-compatible change that changed auint32into auint64(or vice-versa) was forbidden because it would end in a non-backward-compatible Iceberg change (fromlongtostringor vice-versa). Now it's possible. This is a breaking change for Protobuf tables as the Iceberg column type changes for those uints.Add support for
google.protobuf.Timestamptype in Protobuf. It gets converted to an Icebergtimestamptz.
Fix time_since_last_top_level_fetch_ms to avoid negative values when there are concurrent fetch requests.
Improve the "Cross AZ Kafka Clients" diagnostic to show more than 1 clientId.
Fix a bug in the instance type detection logic for Kubernetes environments that could cause it to fail to detect the instance type in some cases and return "unknown" instead.
Add log message for mTLS authentication that includes certificate serial number and validity period in order to help monitor client certificate expirations.
This functionality is disabled by default and can be controlled with the
-logMTLSCertificateInfoflag orWARPSTREAM_LOG_MTLS_CERTIFICATE_INFOenvironment variable.
Release v757
February 19, 2026
Added a new agent flag
-injectPrincipalHeader(env varWARPSTREAM_INJECT_PRINCIPAL_HEADER) that, when set to a header key name, injects the kafka principal username as a header in each produced record. This allows downstream consumers to identify which user produced each record.Fixes a bug in the ripcord deletion queue that could cause the "last opened sequence" to grow until the agent is restarted, because the agent silently discards files that should be deleted in some circumstances.
Query engine: Fix a bug that caused fields escaped with backticks to not be queryable properly.
Tableflow:
Emit the correct logical type annotation for time fields in Parquet files.
Fix ingestion of Avro records with decimal fields.
Release v756
February 17, 2026
Reject all traffic to HTTP fetch endpoints if mTLS is enabled on the Agents.
Validate SASL credentials in HTTP fetch endpoints even if SASL authentication is not required by the Agents.
Tableflow: fix regression requiring the IngestionBucketURL to be set for datalake clusters (new unreleased feature).
Release v755
February 12, 2026
Add new /v1/kafka/fetch HTTP/JSON endpoint for manually issuing Fetch requests against the Agents.
Add convenience endpoint
GET /v1/kafka/fetch_single_record?topic=TOPIC&partition=PARTITION&offset=OFFSETfor fetching a single record by offset.Add convenience endpoint
GET /v1/kafka/topics/{topic}/partitions/{partition}/records/{offset}as a REST-style alternative for fetching a single record by offset.Due to false positives, skip the Unregistered WarpStream Environment Variables diagnostic if the agents is deployed as a Kubernetes service with a name that begins with "warpstream_" or "warpstream-".
Release v754
February 12, 2026
Fixed a bug introduced in v746 where the Agents could get deadlocked after experiencing tends of thousands of errors.
Release v753
February 11, 2026
[experimental] Add
-disableOutOfRangeOrbitflag (env:WARPSTREAM_DISABLE_OUT_OF_RANGE_ORBIT): when enabled, orbit-managed topics returnKAFKA_STORAGE_ERRORinstead ofOFFSET_OUT_OF_RANGEin the fetch path, preventing clients from resetting offsets when data has not yet been replicated from the source cluster.
Release v752
February 11, 2026
Redact agent key from startup logs.
Tableflow: Fix rare bug in parquet footer length tracking that could cause compaction jobs to fail with "unsupported thrift type" errors when reading input files.
Release v751
February 9, 2026
Fix default value for
-batchMaxCompressedSizeBytesto be 16MB instead of a value higher than the max.
Release v750
February 9, 2026
Warning: There is a problem with that version fixed in v751. Please upgrade to v751 directly and skip v750.
Flushing behaviour update
Before v750, the agent would flush a new file if it was over your configured
-batchMaxSizeBytesvalue, and its default value was 4MiB. This means that the agent would not create files that contain more than 4i of uncompressed data by default.After this release, by default, the Agent will create a new file if it estimates that it's going to be more than 1MiB after compression by default.
In more details:
This version introduces a
-batchMaxCompressedSizeBytesflag (and the corresponding WARPSTREAM_BATCH_MAX_COMPRESSED_SIZE_BYTES environment variable).If you define just
-batchMaxSizeBytes, then-batchMaxCompressedSizeByteswill not be used, the agent will use exactly your uncompressed bytes limit to choose when to create a new file.If you define just
-batchMaxCompressedSizeBytes, then-batchMaxSizeByteswill be automatically set to a very high value (64MiB)If you define no flags, then
-batchMaxCompressedSizeByteswill be set to 1MiB and-batchMaxSizeByteswill be set to 64MiB.If you define both, a new file will be created when it becomes higher than either limit.
SyncGroup handler now returns validation errors (invalid group ID, missing member ID, etc.) embedded in the response instead of as a top-level error. This improves compatibility with Kafka clients and ensures these expected protocol errors are not logged/metriced as server errors.
Tableflow:
Fix BigQuery integration bug, where orphaned tables were preventing table recreation.
Update ingestion to handle empty topics gracefully
Fix timestamp field indexing for JSON format: timezone is not required anymore for fields with type timestamp.
Fix bug in batcher which would increase the number of files flushed when disable_only_flush_after_timeout is set to true.
Include virtual cluster ID in auto-generated client IDs for Managed Data Pipelines. This ensures it works with
VirtualClusterIDClientStrictValidationenabled.Improve performance of metrics code by swapping a mutex for an RWMutex.
Bump franz-go package from v1.18.1 to v1.20.6.
Add low severity diagnostic to detect misspelled environment variables beginning with
WARPSTREAM_.Fix noisy ACL denial logs for "all topics" metadata requests. When clients refresh metadata for all topics, unauthorized topics are now silently filtered without logging denials (per Kafka protocol behavior).
Release v749
February 2, 2026
Tableflow: Support
skip_raw_record_valuesthat doesn't store the raw record values in the produced data files.Bump build to go
1.25.6to fix vulnerabilityCVE-2025-61726.
Release v748
January 30, 2026
Return an error when MTLS is enabled (without
-spiffeMTLSAuthentication) but the agent is unable to determine the username from the client certificate subject.Add a new push diagnostic that fires when the timeout on produce requests is less than 5 seconds. This helps identify clients with misconfigured timeout settings that may cause issues with WarpStream's object storage-based architecture.
Allow clients to reauthenticate via SASL even when the control plane is down for Ripcord mode.
Tableflow:
Add support for custom partitioning.
Add support for compressing data files, default being snappy.
New metrics:
warpstream.tableflow_partitions_count: Total number of table partitions in the cluster.warpstream.tableflow_partitions_limit: Maximum number of table partitions allowed in the cluster.
Release v747
January 29, 2026
Buffer audit logs agent side in case of failure to publish them.
Patch CVE-2025-15467 & CVE-2025-69419 vulnerabilities in libssl3/libcrypto3.
Tableflow:
Fix decoding of JSON records with date fields serialized in the "YYYY-MM-DD" format.
Update how we track source data timestamp metadata (kafka timestamps) for more efficient retention enforcement.
Release v746
January 27, 2026
Flushes will wait for the entire batch timeout even if the batch max size bytes limit is exceeded. Files will be split and flushed in parallel in accordance to the batch max size bytes limit.
Release v745
January 23, 2026
Add support for SASL
OAUTHBEARERauthentication mechanism in the WarpStream Agent for Kafka clients that support it.New flags and environment variables:
-saslOAuthIssuerURL/WARPSTREAM_SASL_OAUTH_ISSUER_URL: The OAuth issuer URL used to validate tokens presented by clients.-saslOAuthAudience/WARPSTREAM_SASL_OAUTH_AUDIENCE: The expected audience claim in the OAuth tokens presented by clients.When these settings are configured, the Agent will accept OAuth tokens from clients and validate them against the specified issuer and audience.
ACL rules can be created with OAuth principals in the format
User:<subject>to allow or deny access based on the subject claim in the token.Tableflow: Add support for Protobuf schemas.
Release v744
January 21, 2026
Fix issue with lightning topics configuration validation in previous versions that would prevent the agents from starting on some machines (introduced in v737)
Tableflow: Add memory safeguard to prevent potential OOM when ingesting data spanning many partitions.
Release v743
This version of the agent panics at startup on some machines with a high CPU count. Upgrade to v744 or higher if you have this problem. The exact error message is
January 20, 2026
Tableflow: Optimize ingestion by seeking to offsets that correspond to records to speed up the ingestion of topic with large offset gaps in the beginning.
Returns the "invalid topic" error rather than the "kafka storage error" when attempting to fetch from a topic name that does not exist. This is usually gated from the kafka client though.
The WarpStream agent can now create WarpStream lightning topics.
The WarpStream agent can now be started in ripcord mode, with
-enableRipcordor by setting theWARPSTREAM_ENABLE_RIPCORDenvironment variable totrue. See the documentation for more details.
Release v742
This version of the agent panics at startup on some machines with a high CPU count. Upgrade to v744 or higher if you have this problem. The exact error message is
January 19, 2026
Add additional attributes i.e.
client_idandusernameto shadow ACL logs.Enable SASL Authentication automatically for Managed Data Pipelines when ACL shadowing is enabled.
Put back tag
virtual_cluster_idandvirtual_cluster_nametoagent_kafka_request_outcomemetric that got removed by mistake in v740.Fix bug in ACL Shadowing to stop emitting false-positive deny diagnostics.
Release v741
This version of the agent panics at startup on some machines with a high CPU count. Upgrade to v744 or higher if you have this problem. The exact error message is
January 15, 2026
Update playground url to point to the
api.warpstream.cominstead ofconsole.warpstream.com.Please upgrade to this release for playground functionality to continue working.
Rename
-consoleURLto-apiURLflags in playground mode.
Release v740
This version of the agent panics at startup on some machines with a high CPU count. Upgrade to v744 or higher if you have this problem. The exact error message is
January 14, 2026
Downgrade gosnowflake dependency to remove glibc error related to cgo execution.
Fail to start tableflow agents if incorrect roles are provided / configured.
Add
warpstream_agent_acl_deniedmetric to track ACL denials.Treat more kafka server errors as
canceledinstead oferrorif the errors are indicative of the client disconnecting.
Release v739
This version of the agent panics at startup on some machines with a high CPU count. Upgrade to v744 or higher if you have this problem. The exact error message is
Note: This release contains a glibc/cgo error due to the Bento upgrade. Please use v740 instead.
January 12, 2026
Return COORDINATOR_LOAD_IN_PROGRESS instead of KAFKA_STORAGE_ERROR as the generic error code for consumer group coordinator RPCs (JoinGroup, SyncGroup, Heartbeat, LeaveGroup, DescribeGroups, DeleteGroups, ListGroups, OffsetDelete, OffsetFetch) and TxnOffsetCommit. This improves compatibility with the Java consumer client which will automatically retry COORDINATOR_LOAD_IN_PROGRESS errors for these RPCs, but not KAFKA_STORAGE_ERROR.
Tableflow: Fix BigQuery integration to handle table recreation. When a datalake table is recreated with a new UUID, the BigQuery external table is now automatically dropped and recreated to point to the new metadata location. Previously, updates would fail because BigQuery validates that both old and new metadata files exist.
Merge batcher related metrics into single metrics with a
nametag:warpstream.xxx_batcher_batches_count->warpstream.batcher_batches_countwarpstream.xxx_batcher_batches_distribution->warpstream.batcher_batches_distributionwarpstream.xxx_batcher_called->warpstream.batcher_called
Fix bug in Fetch logic that could cause massive amounts of overfetching if clients (like librdkafka) sent fetch requests where the value of partition max bytes was >> the value of fetch max bytes for the entire request.
Reduce default value of
kafkaMaxFetchRequestBytesUncompressedOverrideandkafkaMaxFetchPartitionBytesUncompressedOverridefrom 1GiB to 256MiB. Now that the fetch code has pre-fetching logic, requesting huge amounts of data in a single fetch request is not nearly as useful so we should not allow it by default.Upgrade Bento to v1.14.1 to fix a regression where functions with optional arguments were not being honored.
Release v738
This version of the agent panics at startup on some machines with a high CPU count. Upgrade to v744 or higher if you have this problem. The exact error message is
January 5, 2026
Add
describe-broker-configs,describe-groups,describe-log-dirs, anddescribe-topic-configscommands to thewarpstream agent clibetacommand for inspecting broker, consumer group, log directory, and topic configuration respectively.Add
client_aztag to metricswarpstream_agent_kafka_fetch_compressed_bytes_counterandwarpstream_agent_kafka_produce_compressed_bytes_counter. Theclient_aztag prioritizes using the availability zone set in the client ID, otherwise it uses the resolved client ID from the Agent's subnet mapping. If neither is provided, then a value ofnoneis set.Bump
github.com/eclipse/paho.mqtt.golangto fixCVE-2025-10543