live wire
▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent▸Graph-repair retrieval cut F1 by 0.126 on one suite; a learned router used fewer tokens than always-on retrieval in all sixLin et al. / arXiv▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent▸Graph-repair retrieval cut F1 by 0.126 on one suite; a learned router used fewer tokens than always-on retrieval in all sixLin et al. / arXiv
nl2sql.ai
guideDeployment guide

AWS brought managed Kafka replication to GovCloud—but automatic topic discovery has a gap

MSK Replicator now spans both AWS GovCloud regions and carries offsets, ACLs and topic settings. Teams still need to design around asynchronous replication and a documented new-topic window.

By The News Desk· Nov 7, 2026the quick take — two AI hosts go live when you do

AWS has made Amazon MSK Replicator available in both AWS GovCloud (US-East) and GovCloud (US-West), giving regulated teams a managed route for copying Kafka streams between regions and into Amazon MSK Provisioned from external Kafka clusters. The launch matters for analytics and agent systems that depend on continuously refreshed event data, but it should not be read as a zero-loss failover guarantee.

What the service carries

AWS says MSK Replicator performs asynchronous replication and automatically scales its underlying resources. In addition to records, it can replicate topic configurations, access-control lists and consumer-group offsets. Those offsets are the practical handoff point for applications that need to resume consumption after a regional failure rather than replaying an entire stream or maintaining a separate offset-synchronization system.

The service supports cross-region and same-region patterns. AWS documents aggregation of multiple Kafka clusters into one analytics cluster, multi-region applications, lower-latency regional copies and migration from self-managed Kafka as supported uses. For replication between Amazon MSK clusters, however, the source and target must be in the same AWS account.

The automatic-topic caveat

The most important operational detail sits in the replication documentation. By default, replication starts at the latest offset. Teams can instead select the earliest offset when creating the replicator if they need existing records copied.

When “Detect and copy new topics” is enabled, AWS says discovering and creating a new source topic or partition on the target can take up to 30 seconds. Messages produced before that target topic exists are not replicated. That creates a specific failure mode for dynamic workloads: the replicator can be healthy while the first records of a newly created topic never reach the recovery region.

The safe deployment pattern is therefore explicit rather than magical. Pre-create critical topics on the target, or add a provisioning gate that waits for target readiness before producers publish. If neither is possible, treat the first records on dynamically created topics as potentially absent and design reconciliation around the authoritative source.

What failover still requires

Replication latency varies with regional distance, cluster throughput and partition counts, according to AWS. Replicator resources run in the target region, records are buffered in memory rather than stored by the service, and traffic is encrypted in transit. AWS also creates target topics with replication factor three, which operators can change afterward.

For GovCloud teams, the new regional availability removes custom replication infrastructure from the critical path. It does not remove the need to test recovery-point objectives, topic-creation workflows and consumer cutover. The useful promise is managed replication of data and Kafka metadata—not synchronous mirroring.

sources

Filed by The News Desk. Corrections: desk@nl2sql.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk