# schema-evolution

The practice of safely changing schemas over time while maintaining compatibility with existing data producers and consumers.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Aderant modernizes analytics data pipeline with Apache Iceberg and AWS Lambda

DevFeed: [Aderant modernizes analytics data pipeline with Apache Iceberg and AWS Lambda](<https://devfeed.tech/articles/aderant-modernizes-analytics-data-pipeline-with-apache-iceberg-and-aws-lambda-141916.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/architecture/aderant-modernizes-analytics-data-pipeline-with-apache-iceberg-and-aws-lambda/>)

Author: Sham Birbahadur

Published: 2026-11-19T00:36:23Z

Content type: article

Language: en

Sources: [AWS Architecture Blog](<https://devfeed.tech/sources/aws-architecture-blog.md>)

Topics: [Analytics Pipeline](<https://devfeed.tech/topics/analytics-pipeline.md>), [Apache Iceberg](<https://devfeed.tech/topics/apache-iceberg.md>), [AWS Glue](<https://devfeed.tech/topics/aws-glue.md>), [event-driven data processing](<https://devfeed.tech/topics/event-driven-data-processing.md>), [streaming data analytics](<https://devfeed.tech/topics/streaming-data-analytics.md>), [Event-Streaming](<https://devfeed.tech/topics/event-streaming.md>), [Apache Spark](<https://devfeed.tech/topics/spark.md>), [AWS Database Migration Service](<https://devfeed.tech/topics/aws-database-migration-service.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>), [parquet](<https://devfeed.tech/topics/parquet.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [acid](<https://devfeed.tech/tags/acid.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [aggregation](<https://devfeed.tech/tags/aggregation.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-glue](<https://devfeed.tech/tags/aws-glue.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [batch](<https://devfeed.tech/tags/batch.md>), [change-data-capture](<https://devfeed.tech/tags/change-data-capture.md>), [cost](<https://devfeed.tech/tags/cost.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [data-pipeline](<https://devfeed.tech/tags/data-pipeline.md>), [event-driven](<https://devfeed.tech/tags/event-driven.md>), [faster](<https://devfeed.tech/tags/faster.md>), [iceberg](<https://devfeed.tech/tags/iceberg.md>), [legal](<https://devfeed.tech/tags/legal.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [queries](<https://devfeed.tech/tags/queries.md>)

### AI overview

Aderant replaced Stridyn's 15-minute batch pipeline with an event-driven medallion architecture that processes CDC changes from 700 client environments in single-digit seconds to bronze-layer Apache Iceberg tables. AWS DMS delivers Parquet files to S3; S3 notifications and SQS invoke Lambda for ingestion, while scheduled AWS Glue jobs transform data through silver and gold layers. Incremental Glue jobs handle 77 standard gold tables; 34 complex tables use Iceberg materialized views and snapshot comparisons to send changed rows to native Amazon Redshift tables. Aderant reports 10-26x faster queries on native Redshift tables, under-100-millisecond dashboard queries, and 77 percent lower pipeline compute costs versus streaming alternatives. The account says this approach supports schema changes and concurrent tenant workloads; it also describes a possible future Kinesis path for high-volume tenants.

### Source excerpt

Learn how Aderant modernized the data pipeline behind its Stridyn legal analytics platform with Apache Iceberg, AWS Lambda, and AWS Glue, moving from 15-minute batch cycles to an event-driven medallion architecture that processes change data capture events in single-digit seconds for 700 tenants, with 10-26x faster queries and 77 percent lower cost.

## Data Contracts

DevFeed: [Data Contracts](<https://devfeed.tech/articles/data-contracts-142435.md>)

Original publisher: [Read original article](<https://martinfowler.com/articles/data-contracts.html>)

Author: Martin Fowler (martin@martinfowler.com)

Published: 2026-11-18T14:02:00Z

Content type: article

Language: en

Sources: [Martin Fowler](<https://devfeed.tech/sources/martin-fowler.md>)

Topics: [data](<https://devfeed.tech/topics/data.md>), [schema design](<https://devfeed.tech/topics/schema-design.md>), [Data Quality](<https://devfeed.tech/topics/data-quality.md>), [semantic-layer](<https://devfeed.tech/topics/semantic-layer.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [contracts](<https://devfeed.tech/tags/contracts.md>), [data](<https://devfeed.tech/tags/data.md>), [data-contracts](<https://devfeed.tech/tags/data-contracts.md>), [data-products](<https://devfeed.tech/tags/data-products.md>), [datasets](<https://devfeed.tech/tags/datasets.md>), [enterprises](<https://devfeed.tech/tags/enterprises.md>), [guarantees](<https://devfeed.tech/tags/guarantees.md>), [interfaces](<https://devfeed.tech/tags/interfaces.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [practices](<https://devfeed.tech/tags/practices.md>), [robustness](<https://devfeed.tech/tags/robustness.md>), [services](<https://devfeed.tech/tags/services.md>)

### AI overview

Data contracts make a provider's dataset promises explicit and machine-readable, covering schema and meaning, quality checks, service levels, usage terms, ownership, and access details. The article presents ODCS as a YAML standard for these contracts and recommends validating promises automatically in CI/CD and against production data. Versioning helps detect breaking changes and phase in replacements; contracts can also connect to data products, ontologies, and marketplaces, giving consumers and AI agents context for finding, joining, and using data. They require ongoing effort and accountable ownership, so the article recommends starting with cross-team data interfaces where quality problems, broken pipelines, or miscommunication are costly.

### Source excerpt

Data contracts are a way to describe the contents and guarantees of datasets. Simon Harrer and Arif Wider describe in detail what they are and how to use them. They apply practices from API design to data by treating them as data-providing services - such as data products - whose interfaces we want to define as clearly as possible. This approach significantly increases the robustness of large-scale data landscapes, and gives both people and AI agents the explicit, trustworthy metadata they need to work with data autonomously, which is why more and more enterprises are adopting them. more...

## Understanding Enterprise Customer Engagement With the Modern Data Stack | Blog | Fivetran

DevFeed: [Understanding Enterprise Customer Engagement With the Modern Data Stack | Blog | Fivetran](<https://devfeed.tech/articles/understanding-enterprise-customer-engagement-with-the-modern-data-stack-blog-fivetran-140265.md>)

Original publisher: [Read original article](<https://wf.fivetran.com/blog/understanding-enterprise-customer-engagement-with-the-modern-data-stack>)

Author: Ross Katz

Published: 2026-11-18T05:58:59Z

Content type: article

Language: en

Sources: [Fivetran Blog](<https://devfeed.tech/sources/fivetran-blog.md>)

Topics: [analytics stack](<https://devfeed.tech/topics/analytics-stack.md>), [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [elt](<https://devfeed.tech/topics/elt.md>), [etl](<https://devfeed.tech/topics/etl.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>), [Data Management](<https://devfeed.tech/topics/data-management.md>)

Tags: [analytics-workloads](<https://devfeed.tech/tags/analytics-workloads.md>), [api](<https://devfeed.tech/tags/api.md>), [azure-synapse](<https://devfeed.tech/tags/azure-synapse.md>), [b2b](<https://devfeed.tech/tags/b2b.md>), [bigquery](<https://devfeed.tech/tags/bigquery.md>), [change-data-capture](<https://devfeed.tech/tags/change-data-capture.md>), [cloud-data-warehouse](<https://devfeed.tech/tags/cloud-data-warehouse.md>), [connectors](<https://devfeed.tech/tags/connectors.md>), [crm](<https://devfeed.tech/tags/crm.md>), [customer-engagement](<https://devfeed.tech/tags/customer-engagement.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [modern-data-stack](<https://devfeed.tech/tags/modern-data-stack.md>)

### AI overview

Companies serving both individual and enterprise customers need separate, evolving data models and processes to understand leads, customer journeys, renewals, and retention. The article argues that operational databases, CRMs, and ERPs are built to drive actions, so customizing them for changing analytics needs can increase overhead, maintenance, and performance problems. It recommends moving operational data into a cloud data warehouse, analyzing it there, and sending useful results back to business systems. Custom pipelines can require substantial setup and upkeep, with challenges including API limits, change data capture, source schema changes, and expanding access needs. The proposed Modern Data Stack uses Fivetran connectors to load source data into warehouses such as BigQuery, Snowflake, Redshift, or Azure Synapse, alongside analytics tools and reverse ETL. This can shift engineering effort from migration plumbing to analysis, though the article presents these benefits as its recommendation rather than quantified results.

### Source excerpt

Companies with B2B and B2C channels face complex management challenges that a modern data stack can solve.

## Getting started with Apache Polaris Catalog in Fivetran's Managed Data Lake Service | Blog | Fivetran

DevFeed: [Getting started with Apache Polaris Catalog in Fivetran's Managed Data Lake Service | Blog | Fivetran](<https://devfeed.tech/articles/getting-started-with-apache-polaris-catalog-in-fivetran-s-managed-data-lake-service-blog-fivetran-140235.md>)

Original publisher: [Read original article](<https://wf.fivetran.com/blog/getting-started-with-apache-polaris-catalog-in-fivetrans-managed-data-lake-service>)

Author: Andrew Madson

Published: 2026-11-18T04:00:44Z

Content type: tutorial

Language: en

Sources: [Fivetran Blog](<https://devfeed.tech/sources/fivetran-blog.md>)

Topics: [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [data lake](<https://devfeed.tech/topics/data-lake.md>), [Apache Spark](<https://devfeed.tech/topics/spark.md>), [parquet](<https://devfeed.tech/topics/parquet.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>), [database-consistency](<https://devfeed.tech/topics/database-consistency.md>)

Tags: [acid](<https://devfeed.tech/tags/acid.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [apache](<https://devfeed.tech/tags/apache.md>), [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [apache-polaris](<https://devfeed.tech/tags/apache-polaris.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [configure](<https://devfeed.tech/tags/configure.md>), [data-engineer](<https://devfeed.tech/tags/data-engineer.md>), [data-lake](<https://devfeed.tech/tags/data-lake.md>), [engines](<https://devfeed.tech/tags/engines.md>), [fivetran](<https://devfeed.tech/tags/fivetran.md>), [getting-started](<https://devfeed.tech/tags/getting-started.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [managed](<https://devfeed.tech/tags/managed.md>), [matters](<https://devfeed.tech/tags/matters.md>), [popular](<https://devfeed.tech/tags/popular.md>), [practices](<https://devfeed.tech/tags/practices.md>), [query](<https://devfeed.tech/tags/query.md>), [service](<https://devfeed.tech/tags/service.md>)

### AI overview

Fivetran's Managed Data Lake Service uses Apache Polaris as its default Iceberg REST catalog, maintaining table metadata for Parquet data in supported cloud destinations. Query tables through the catalog so engines read committed snapshots, apply deletes, follow schema changes, and avoid hard-coded file paths; Fivetran alone can modify catalog metadata. The article gives OAuth2 setup examples for Spark, DuckDB, Snowflake, and Trino/Starburst. Requirements and capabilities differ: Spark needs Iceberg 1.9.0+ with Spark 3.4 or 3.5; DuckDB's REST support is experimental, supports SELECT and time travel, and is currently limited to S3-compatible storage; Snowflake external-table reads are generally available while writes are in preview, with configurable refresh; Trino/Starburst use REST catalog properties and vended credentials. Protect metadata files and configure refresh and snapshot retention for freshness and time-travel needs.

### Source excerpt

Why the catalog matters, how to configure it with popular query engines, and the essential best practices every data engineer should follow.

## Managing Distributed Schemas with Confidence: Atlas Now Supports YugabyteDB

DevFeed: [Managing Distributed Schemas with Confidence: Atlas Now Supports YugabyteDB](<https://devfeed.tech/articles/managing-distributed-schemas-with-confidence-atlas-now-supports-yugabytedb-136073.md>)

Original publisher: [Read original article](<https://www.yugabyte.com/blog/managing-distributed-schemas-with-confidence-atlas-now-supports-yugabytedb/>)

Author: Yaron Parasol

Published: 2026-11-16T13:00:04Z

Content type: release

Language: en

Sources: [The Distributed SQL Blog](<https://devfeed.tech/sources/the-distributed-sql-blog.md>)

Topics: [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>), [Apache Cassandra](<https://devfeed.tech/topics/cassandra.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [apply](<https://devfeed.tech/tags/apply.md>), [atlas](<https://devfeed.tech/tags/atlas.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [colocation](<https://devfeed.tech/tags/colocation.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [distributed-sql](<https://devfeed.tech/tags/distributed-sql.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [hash](<https://devfeed.tech/tags/hash.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [plan](<https://devfeed.tech/tags/plan.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [range](<https://devfeed.tech/tags/range.md>), [safely](<https://devfeed.tech/tags/safely.md>), [schema](<https://devfeed.tech/tags/schema.md>), [schemas](<https://devfeed.tech/tags/schemas.md>), [sharding](<https://devfeed.tech/tags/sharding.md>), [tablet](<https://devfeed.tech/tags/tablet.md>), [teams](<https://devfeed.tech/tags/teams.md>), [workflows](<https://devfeed.tech/tags/workflows.md>), [yugabytedb](<https://devfeed.tech/tags/yugabytedb.md>)

### AI overview

Atlas Pro supports YugabyteDB through its `ysql://` driver, modeling distribution settings such as sharding and colocation alongside ordinary schema objects. It inspects live databases, includes layout choices in generated DDL and plans, and supports review and rollout through local apply, CI pull request plans, and environment specific deployments. The examples show hash sharding for a write heavy orders table and a range sharded index for time bounded scans; range sharding can speed those scans but concentrates new writes on the current month's tablet. Atlas blocks in place changes to table colocation, applies split directives only at creation, and does not treat automatic tablet splitting as schema drift. Migration linting and review policies can hold risky changes for approval; the post says index sharding cannot be changed in place, so a wrong choice may require rebuilding the index.

### Source excerpt

Atlas, the open-source schema-as-code product, now supports YugabyteDB's extensions to the PostgreSQL schema. It can understand and manage the distributed constructs that make YugabyteDB unique, including hash and range sharding, tablet splitting and colocation, and tablespaces for geo-placement. Teams can describe their full distributed schema in code, and Atlas will safely plan, validate, and apply changes. This blog walks through how to set up Atlas with YugabyteDB and demonstrates these workflows in action. The post Managing Distributed Schemas with Confidence: Atlas Now Supports YugabyteDB appeared first on Yugabyte.

## Oracle to ClickHouse: CDC, Batch & Type Mapping Guide

DevFeed: [Oracle to ClickHouse: CDC, Batch & Type Mapping Guide](<https://devfeed.tech/articles/oracle-to-clickhouse-cdc-batch-type-mapping-guide-121705.md>)

Original publisher: [Read original article](<https://estuary.dev/blog/oracle-to-clickhouse>)

Author: Seán Whelan

Published: 2026-11-06T12:26:57Z

Content type: tutorial

Language: en

Sources: [Estuary](<https://devfeed.tech/sources/estuary.md>)

Topics: [Oracle Database](<https://devfeed.tech/topics/oracle-database.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>), [data type](<https://devfeed.tech/topics/data-type.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>)

Tags: [batch](<https://devfeed.tech/tags/batch.md>), [cdc](<https://devfeed.tech/tags/cdc.md>), [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [guide](<https://devfeed.tech/tags/guide.md>), [mapping](<https://devfeed.tech/tags/mapping.md>), [oracle](<https://devfeed.tech/tags/oracle.md>), [type](<https://devfeed.tech/tags/type.md>)

### AI overview

For Oracle tables that change continuously, the excerpt recommends log-based CDC through LogMiner: it reads redo logs in SCN order, captures hard deletes, and resumes from a checkpoint if the required archived logs remain available. Setup requires ARCHIVELOG mode, supplemental logging, adequate log retention, and primary keys on replicated tables. ClickHouse stores changes as row versions; ReplacingMergeTree collapses versions by sorting key during merges, while queries may need FINAL before merges complete. The excerpt also explains tombstones and delete markers, key-change handling, type-mapping pitfalls (especially Oracle DATE and NUMBER), insert batching, and recovery limits. Method choice depends on needs: file exports and scheduled batch copies suit snapshots or reporting; Debezium with Kafka fits teams already running that stack, though its ClickHouse sink needs pre-created tables and does not support deletes directly; ClickPipes has no Oracle CDC source. Estuary is presented as a managed LogMiner capture and ClickHouse materialization, with configurable sync frequency and documented type limitations, including skipped LOB and binary columns.

### Source excerpt

Move data from Oracle to ClickHouse: map types, handle updates and deletes with ReplacingMergeTree, and compare 4 CDC and batch methods.

## Kafka to ClickHouse: Streaming Ingestion, Duplicates & Tombstones Guide

DevFeed: [Kafka to ClickHouse: Streaming Ingestion, Duplicates & Tombstones Guide](<https://devfeed.tech/articles/kafka-to-clickhouse-streaming-ingestion-duplicates-tombstones-guide-121703.md>)

Original publisher: [Read original article](<https://estuary.dev/blog/kafka-to-clickhouse>)

Author: Seán Whelan

Published: 2026-11-06T12:26:41Z

Content type: article

Language: en

Sources: [Estuary](<https://devfeed.tech/sources/estuary.md>)

Topics: [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [Event-Streaming](<https://devfeed.tech/topics/event-streaming.md>), [self-hosted databases vs managed services](<https://devfeed.tech/topics/self-hosted-databases-vs-managed-services.md>), [table-partitioning](<https://devfeed.tech/topics/table-partitioning.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>), [Amazon MSK](<https://devfeed.tech/topics/amazon-msk.md>), [Confluent Cloud](<https://devfeed.tech/topics/confluent-cloud.md>), [Apache Iceberg](<https://devfeed.tech/topics/apache-iceberg.md>)

Tags: [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [compare](<https://devfeed.tech/tags/compare.md>), [connect](<https://devfeed.tech/tags/connect.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [engine](<https://devfeed.tech/tags/engine.md>), [guarantees](<https://devfeed.tech/tags/guarantees.md>), [guide](<https://devfeed.tech/tags/guide.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [stream](<https://devfeed.tech/tags/stream.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [table](<https://devfeed.tech/tags/table.md>)

### AI overview

Kafka ingestion into ClickHouse is generally at least once, so replayed messages can create duplicates; reliable designs need batching and tables suited to event or keyed data. The article compares the Kafka table engine, ClickPipes, the Kafka Connect sink, and managed pipelines: the engine runs consumers on ClickHouse servers, ClickPipes is recommended for ClickHouse Cloud, and the sink fits teams already running Kafka Connect. For event streams, store partition and offset in a ReplacingMergeTree sorting key; keyed topics with tombstones need ReplacingMergeTree keyed by message key and queries with FINAL. Tombstone support differs: ClickPipes can delete rows in exactly-once mode or mark them deleted, while the Connect sink lists deletes as unsupported and the table engine's documentation does not describe null-value messages. Retention limits recovery, and compaction can remove tombstones after the configured retention period. Large, infrequent inserts reduce part pressure; monitor lag and active parts. The article also describes Estuary capture and materialization, which keeps Kafka progress in its own checkpoints and writes to ClickHouse on a configurable schedule.

### Source excerpt

Stream Kafka to ClickHouse with the Kafka table engine, ClickPipes or Kafka Connect. Compare 4 methods, delivery guarantees and duplicate handling.

## Introducing Apache Spark® 4.3 - Now available in Databricks Runtime 19

DevFeed: [Introducing Apache Spark® 4.3 - Now available in Databricks Runtime 19](<https://devfeed.tech/articles/introducing-apache-spark-4-3-now-available-in-databricks-runtime-19-117923.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/introducing-apache-spark-43-now-available-databricks-runtime-19>)

Author: Jungtaek Lim; Wenchen Fan; Andreas Neumann; Serge Rielau; Hyukjin Kwon; Jerry Peng; DB Tsai; Daniel Tenedorio; Xiao Li; Reynold Xin

Published: 2026-11-05T00:00:00Z

Content type: release

Language: en

Sources: [Databricks](<https://devfeed.tech/sources/databricks.md>)

Topics: [Apache Spark](<https://devfeed.tech/topics/spark.md>), [streaming data analytics](<https://devfeed.tech/topics/streaming-data-analytics.md>), [Stateful](<https://devfeed.tech/topics/stateful.md>), [Event-Streaming](<https://devfeed.tech/topics/event-streaming.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [apache-arrow](<https://devfeed.tech/topics/apache-arrow.md>), [parquet](<https://devfeed.tech/topics/parquet.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>), [databricks](<https://devfeed.tech/topics/databricks.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>), [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>)

Tags: [aggregation](<https://devfeed.tech/tags/aggregation.md>), [apache](<https://devfeed.tech/tags/apache.md>), [apache-spark](<https://devfeed.tech/tags/apache-spark.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [spark](<https://devfeed.tech/tags/spark.md>), [stateful](<https://devfeed.tech/tags/stateful.md>)

### AI overview

Apache Spark 4.3 extends Structured Streaming's Real-Time Mode with stateful aggregation, deduplication and custom processing, reporting P99 end-to-end latency below 150 ms across three tested benchmarks; those measurements are not a guarantee for all workloads. It enables continuous data flow through concurrent stage scheduling and pipelined shuffles, while retaining Spark's state store and checkpointing. The release also adds Auto CDC SCD Type 2 history through Python, SQL and Spark Connect, requiring a catalog connector that supports Data Source V2 row-level operations (built-in Parquet does not). Other additions include opt-in shuffle-free execution for eligible small queries, Spark Connect session and operation visibility, JSON and VARIANT processing, and ASOF JOIN and nanosecond timestamp previews that may change. Spark 4.3 starts a quarterly feature-release cadence.

### Source excerpt

IntroductionApache Spark 4.3 brings stateful processing to Real-Time Mode, achieving...

## How Procore is powering construction analytics with OpenSharing

DevFeed: [How Procore is powering construction analytics with OpenSharing](<https://devfeed.tech/articles/how-procore-is-powering-construction-analytics-with-opensharing-105667.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/how-procore-powering-construction-analytics-opensharing-0>)

Author: Krishan Kumar

Published: 2026-10-29T00:29:00Z

Content type: article

Language: en

Sources: [Databricks](<https://devfeed.tech/sources/databricks.md>)

Topics: [databricks](<https://devfeed.tech/topics/databricks.md>), [Analytics Pipeline](<https://devfeed.tech/topics/analytics-pipeline.md>), [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [Data Quality](<https://devfeed.tech/topics/data-quality.md>), [semantic-layer](<https://devfeed.tech/topics/semantic-layer.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>), [protocols](<https://devfeed.tech/topics/protocols.md>), [DataOps](<https://devfeed.tech/topics/dataops.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-use](<https://devfeed.tech/tags/ai-use.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [asia](<https://devfeed.tech/tags/asia.md>), [australia](<https://devfeed.tech/tags/australia.md>), [automated](<https://devfeed.tech/tags/automated.md>), [availability](<https://devfeed.tech/tags/availability.md>), [azure](<https://devfeed.tech/tags/azure.md>), [bi](<https://devfeed.tech/tags/bi.md>), [bi-tools](<https://devfeed.tech/tags/bi-tools.md>), [bigquery](<https://devfeed.tech/tags/bigquery.md>), [budget](<https://devfeed.tech/tags/budget.md>), [business](<https://devfeed.tech/tags/business.md>), [company](<https://devfeed.tech/tags/company.md>), [customers](<https://devfeed.tech/tags/customers.md>), [data](<https://devfeed.tech/tags/data.md>)

### AI overview

Procore replaced its API-driven Analytics 1.0 pipeline, limited to at most three daily refreshes, with Analytics 2.0 built on Databricks and OpenSharing. Curated gold-layer data is shared across regions, with Unity Catalog governance and automated per-user, per-project entitlements. Databricks customers can receive shares natively; others connect through OpenSharing's protocol and client libraries, including from BI tools and other platforms. Recipients can consume full tables or Change Data Feed updates. Procore says the new pipeline expanded its extract catalog to hundreds of tables in less than half the time the first version took to build its baseline, and customers can schedule refreshes according to their tools' capabilities. To manage downstream disruption, it gives six weeks' notice for four annual breaking-change releases and three weeks for twelve non-breaking releases.

### Source excerpt

Connecting an industry built on disconnected dataConstruction runs on data that rarely sits in one place...

## How Procore is powering construction analytics with OpenSharing

DevFeed: [How Procore is powering construction analytics with OpenSharing](<https://devfeed.tech/articles/how-procore-is-powering-construction-analytics-with-opensharing-112964.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/how-procore-powering-construction-analytics-opensharing>)

Author: Krishan Kumar

Published: 2026-10-29T00:29:00Z

Content type: article

Language: en

Sources: [Databricks](<https://devfeed.tech/sources/databricks.md>)

Topics: [databricks](<https://devfeed.tech/topics/databricks.md>), [Analytics Pipeline](<https://devfeed.tech/topics/analytics-pipeline.md>), [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [Data Quality](<https://devfeed.tech/topics/data-quality.md>), [semantic-layer](<https://devfeed.tech/topics/semantic-layer.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>), [protocols](<https://devfeed.tech/topics/protocols.md>), [DataOps](<https://devfeed.tech/topics/dataops.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-use](<https://devfeed.tech/tags/ai-use.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [analytics-pipeline](<https://devfeed.tech/tags/analytics-pipeline.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [area](<https://devfeed.tech/tags/area.md>), [asia](<https://devfeed.tech/tags/asia.md>), [australia](<https://devfeed.tech/tags/australia.md>), [company](<https://devfeed.tech/tags/company.md>), [construction](<https://devfeed.tech/tags/construction.md>), [customers](<https://devfeed.tech/tags/customers.md>), [data](<https://devfeed.tech/tags/data.md>), [one](<https://devfeed.tech/tags/one.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Procore Analytics 2.0 replaces a SQL Server pipeline fed by public API extractions--which allowed at most three refreshes per day--with Databricks OpenSharing. Procore cleans, validates, and models data in a multi-region medallion pipeline, then shares gold tables to customer environments. Customers without Databricks connect with an OpenSharing token and client libraries; Databricks customers can receive shares natively. Unity Catalog permissions are reconciled automatically per user and project, and Change Data Feed lets recipients sync only updates or the full dataset. Procore reports expanding its extract catalog to hundreds of tables in less than half the time taken to build the first version, while customers can schedule refreshes to suit their tools. It also sets release notice periods: six weeks for four annual breaking changes and three weeks for twelve non-breaking releases. The source describes the architecture and reported benefits but provides no measured refresh latency or quantified cost comparison.

### Source excerpt

Connecting an industry built on disconnected dataConstruction runs on data that rarely sits in one place...

## Estuary Expands PostgreSQL CDC with Targeted Backfills and Scalable Discovery

DevFeed: [Estuary Expands PostgreSQL CDC with Targeted Backfills and Scalable Discovery](<https://devfeed.tech/articles/estuary-expands-postgresql-cdc-with-targeted-backfills-and-scalable-discovery-105459.md>)

Original publisher: [Read original article](<https://www.postgresql.org/about/news/estuary-expands-postgresql-cdc-with-targeted-backfills-and-scalable-discovery-3419/>)

Published: 2026-10-28T00:00:00Z

Content type: release

Language: en

Sources: [PostgreSQL news](<https://devfeed.tech/sources/postgresql-news.md>)

Topics: [neki](<https://devfeed.tech/topics/neki.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>)

Tags: [cdc](<https://devfeed.tech/tags/cdc.md>), [change-data-capture](<https://devfeed.tech/tags/change-data-capture.md>), [change-detection](<https://devfeed.tech/tags/change-detection.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [estuary](<https://devfeed.tech/tags/estuary.md>), [filter](<https://devfeed.tech/tags/filter.md>), [improve-reliability](<https://devfeed.tech/tags/improve-reliability.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [queries](<https://devfeed.tech/tags/queries.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [replication](<https://devfeed.tech/tags/replication.md>)

### AI overview

Estuary's PostgreSQL CDC updates add controls for recovery and large-schema discovery. An Additional Backfill Filter applies a SQL expression to one table's backfill queries, which can limit rows reread; it does not affect ongoing CDC, and changing it requires another backfill. Discovery filters can include selected schemas, exclude schemas, use glob-based table patterns, and optionally find tables outside the PostgreSQL publication. Metadata discovery runs in smaller groups for improved reliability. Active captures can also set their rediscovery interval (15 minutes by default) to tune the tradeoff between detecting new tables or schema changes sooner and catalog-query activity. The connector uses PostgreSQL logical replication and supports PostgreSQL 10.0 and later, including self-hosted and managed services.

### Source excerpt

Estuary has released several updates to its PostgreSQL change data capture (CDC) connector focused on backfill recovery, discovery at scale, and schema-change detection. Targeted Backfills PostgreSQL capture bindings now support an Additional Backfill Filter, allowing a SQL expression to be applied to backfill queries for an individual table. This can reduce the amount of data that needs to be re-read when only a subset of a large PostgreSQL table needs to be recovered or re-backfilled. For example, teams can use an indexed identifier or timestamp to limit the rows included in a recovery backfill. The filter affects backfills only. Ongoing PostgreSQL CDC continues to capture new changes independently of the filter. Because the SQL expression is applied directly to backfill queries, this is an advanced option and should be configured carefully. Changing the filter requires the affected binding to be backfilled again. Discovery Controls for Large PostgreSQL Schemas Estuary has also added PostgreSQL discovery filters that allow captures to control which tables are surfaced during connector discovery. Captures can now: include only selected PostgreSQL schemas exclude selected schemas discover tables using glob-based table patterns optionally discover tables that are not yet included in the PostgreSQL publication These controls are useful for PostgreSQL environments with large numbers of schemas or tables where only part of the database should participate in a CDC pipeline. Table metadata discovery is also processed in smaller groups to improve reliability when working with databases containing large numbers of tables. Configurable Rediscovery PostgreSQL captures can now configure how frequently Estuary re-runs discovery while a capture is active. Rediscovery is used to detect changes such as newly added tables and schema updates. The default interval is 15 minutes and can be adjusted for environments that require faster or less frequent discovery. This gives PostgreSQL

## Apache Iceberg Schema Evolution for Nested Data: Safe Changes and Compatibility Rules

DevFeed: [Apache Iceberg Schema Evolution for Nested Data: Safe Changes and Compatibility Rules](<https://devfeed.tech/articles/apache-iceberg-schema-evolution-for-nested-data-safe-changes-and-compatibility-rules-102842.md>)

Original publisher: [Read original article](<https://www.dremio.com/blog/apache-iceberg-schema-evolution-for-nested-data-safe-changes-and-compatibility-rules/>)

Author: Alex Merced

Published: 2026-10-27T18:56:58Z

Content type: article

Language: en

Sources: [Dremio](<https://devfeed.tech/sources/dremio.md>)

Topics: [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>), [Apache Iceberg](<https://devfeed.tech/topics/apache-iceberg.md>), [schema design](<https://devfeed.tech/topics/schema-design.md>), [Apache Spark](<https://devfeed.tech/topics/spark.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [data-lakehouse](<https://devfeed.tech/tags/data-lakehouse.md>), [dremio-blog-open-data-insights](<https://devfeed.tech/tags/dremio-blog-open-data-insights.md>), [engine](<https://devfeed.tech/tags/engine.md>), [ids](<https://devfeed.tech/tags/ids.md>), [maps](<https://devfeed.tech/tags/maps.md>), [nested](<https://devfeed.tech/tags/nested.md>), [rules](<https://devfeed.tech/tags/rules.md>), [schema-evolution](<https://devfeed.tech/tags/schema-evolution.md>), [tests](<https://devfeed.tech/tags/tests.md>), [type](<https://devfeed.tech/tags/type.md>)

### AI overview

Iceberg resolves nested fields by stable field ID, which can allow metadata-only additions, drops, renames, and reordering without rewriting files when readers honor IDs. Assign new IDs to added or re-added fields; keep the ID for a rename. New fields should be optional or have defaults, and making optional fields required without defaults can break reads. Map-key type changes cannot be evolved in place and require a rewrite or a new column and migration. Type promotions vary by format version and engine. The excerpt recommends checking metadata IDs, staging changes, and testing reads across every production engine and connector version before rollout; its example reports Spark and Dremio passing while an older Trino connector returned nulls after a rename. If a reader fails compatibility checks, upgrade it, rewrite data, or migrate to a new column, then monitor errors and nulls and retain a rollback snapshot.

### Source excerpt

Evolve nested Iceberg structs, lists, and maps safely using field IDs, nullability, type-promotion rules, defaults, and cross-engine compatibility tests. The post Apache Iceberg Schema Evolution for Nested Data: Safe Changes and Compatibility Rules appeared first on Dremio.

## Migrating from Nessie to Apache Polaris Without Rewriting Iceberg Data

DevFeed: [Migrating from Nessie to Apache Polaris Without Rewriting Iceberg Data](<https://devfeed.tech/articles/migrating-from-nessie-to-apache-polaris-without-rewriting-iceberg-data-102847.md>)

Original publisher: [Read original article](<https://www.dremio.com/blog/migrating-from-nessie-to-apache-polaris-without-rewriting-iceberg-data/>)

Author: Alex Merced

Published: 2026-10-27T18:56:51Z

Content type: tutorial

Language: en

Sources: [Dremio](<https://devfeed.tech/sources/dremio.md>)

Topics: [data migrations](<https://devfeed.tech/topics/data-migrations.md>), [Apache Iceberg](<https://devfeed.tech/topics/apache-iceberg.md>), [versioning](<https://devfeed.tech/topics/versioning.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>), [etl](<https://devfeed.tech/topics/etl.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [parquet](<https://devfeed.tech/topics/parquet.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [apache-polaris](<https://devfeed.tech/tags/apache-polaris.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [data-lakehouse](<https://devfeed.tech/tags/data-lakehouse.md>), [dremio-blog-open-data-insights](<https://devfeed.tech/tags/dremio-blog-open-data-insights.md>), [iceberg](<https://devfeed.tech/tags/iceberg.md>), [migration](<https://devfeed.tech/tags/migration.md>), [rollback](<https://devfeed.tech/tags/rollback.md>)

### AI overview

Iceberg data files can often remain in place during a Nessie-to-Polaris migration by registering the same metadata locations in Polaris. The excerpt recommends freezing writes, inventorying Nessie references and table metadata, planning an explicit mapping for branches and tags, recreating access rules, and validating reads before switching clients in stages. Compare snapshot IDs, row counts, and checksums across catalogs; keep Nessie read-only during a rollback window. Concurrent writes to both catalogs can create split-brain metadata and require human reconciliation. Polaris migration tooling was described as documented on an unreleased branch at the time stated in the text, so verify commands and behavior against the target deployment and test in staging.

### Source excerpt

Plan a Nessie-to-Polaris Iceberg catalog migration that reuses existing object storage, validates table metadata, preserves rollback, and limits downtime. The post Migrating from Nessie to Apache Polaris Without Rewriting Iceberg Data appeared first on Dremio.

## How I Migrated a Live Database to a Many-to-Many Relationship

DevFeed: [How I Migrated a Live Database to a Many-to-Many Relationship](<https://devfeed.tech/articles/how-i-migrated-a-live-database-to-a-many-to-many-relationship-97407.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-i-migrated-a-live-database-to-a-many-to-many-relationship?source=rss>)

Author: Gabriela Colombo Alves Longo

Published: 2026-10-23T08:53:36Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>), [expand and contract migration](<https://devfeed.tech/topics/expand-and-contract-migration.md>), [Database](<https://devfeed.tech/topics/database.md>), [Data Quality](<https://devfeed.tech/topics/data-quality.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [backend](<https://devfeed.tech/tags/backend.md>), [backward-compatible-apis](<https://devfeed.tech/tags/backward-compatible-apis.md>), [clients](<https://devfeed.tech/tags/clients.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [database-backfill](<https://devfeed.tech/tags/database-backfill.md>), [database-schema](<https://devfeed.tech/tags/database-schema.md>), [database-schema-migration](<https://devfeed.tech/tags/database-schema-migration.md>), [event-platform](<https://devfeed.tech/tags/event-platform.md>), [expand-and-contract-migration](<https://devfeed.tech/tags/expand-and-contract-migration.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [graphql-api-compatibility](<https://devfeed.tech/tags/graphql-api-compatibility.md>), [index](<https://devfeed.tech/tags/index.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [many-to-many](<https://devfeed.tech/tags/many-to-many.md>), [many-to-many-relationships](<https://devfeed.tech/tags/many-to-many-relationships.md>), [system-design](<https://devfeed.tech/tags/system-design.md>)

### AI overview

The article describes evolving a live speaker-role feature from one-to-one to many-to-many while keeping existing events and clients working. Version 1 created a default role for every event, migrated existing speakers to it, and made GraphQL `roleId` optional so older clients received the default. Because existing free-text speaker types were sparse and inconsistent, the author used an organizer toggle instead of automatically converting them. For Version 2, a pivot table was added alongside the old foreign key; writes moved to the new table, existing links were backfilled, and reads preferred the pivot table with fallback to the old relationship. This let deployment and backfill proceed without a gap in role data or an API response shape change. The account emphasizes checking data quality and involving teams close to customers when choosing relationship cardinality.

### Source excerpt

How I shipped a feature as a 1:1 relationship, then redesigned it to many-to-many after release, without breaking existing events or clients.

## Kubernetes 1.37: The 10 Changes I'd Actually Care About (and a Pre-Upgrade Checklist)

DevFeed: [Kubernetes 1.37: The 10 Changes I'd Actually Care About (and a Pre-Upgrade Checklist)](<https://devfeed.tech/articles/kubernetes-1-37-the-10-changes-i-d-actually-care-about-and-a-pre-upgrade-checklist-95220.md>)

Original publisher: [Read original article](<https://blog.devops.dev/kubernetes-1-37-the-10-changes-id-actually-care-about-and-a-pre-upgrade-checklist-5210d786c737?source=rss----33f8b2d9a328---4>)

Author: Vivek Raj

Published: 2026-10-22T08:54:59Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [upgrade](<https://devfeed.tech/topics/upgrade.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [container-networking](<https://devfeed.tech/topics/container-networking.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [alpha](<https://devfeed.tech/tags/alpha.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [beta](<https://devfeed.tech/tags/beta.md>), [changes](<https://devfeed.tech/tags/changes.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [devops](<https://devfeed.tech/tags/devops.md>), [external](<https://devfeed.tech/tags/external.md>), [gpu-inference](<https://devfeed.tech/tags/gpu-inference.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-1-37](<https://devfeed.tech/tags/kubernetes-1-37.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [queue](<https://devfeed.tech/tags/queue.md>), [release-notes](<https://devfeed.tech/tags/release-notes.md>), [sre](<https://devfeed.tech/tags/sre.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

### AI overview

The excerpt highlights Kubernetes 1.37 changes with operational impact. HPA can scale workloads to zero using Object or External metrics; CPU and memory metrics cannot wake a zero-Pod workload. API server cache initialization gains streaming etcd reads (with fallback on etcd versions before 3.7), parallel decoding, and bounded requests that may return HTTP 429, so clients should respect Retry-After and back off. Other changes include Beta gang scheduling, Stable Pod certificates that require an external signer, disk-loaded admission policies, and Stable in-tree storage migration. Memory QoS is enabled by default on cgroup v2 but changes nothing without opt-in; TieredReservation can prevent reclaim of Guaranteed Pods' page cache. Before upgrading, check SELinux volume sharing, remove Secret or ConfigMap references from Static Pods, verify cgroup v2, and review deprecated IPVS, kube-dns, and kubectl run -f usage. The article also describes PVC unused status as informational only and whole-Pod checkpoint/restore as Alpha requiring runtime support.

### Source excerpt

I read through the 1.37 release notes and the KEPs behind them so you don't have to. Here's what matters if you run clusters for a living, with the YAML and the GitHub links. Kubernetes 1.37 ("Garhwal") came out on 26 August 2026. It has 67 enhancements: 16 went Stable, 23 went Beta, 27 are new Alpha features, and there's 1 deprecation. Most of those won't change your week. A few of them will, and a couple can break an upgrade if you don't check first. I sorted them the way I'd sort them for my own team: things you get for free, things you can start using now, and things to check before you upgrade. Every section links to the KEP on GitHub. If you only have five minutes, jump to the checklist at the end. Here's what a few of these look like on a real 1.37 cluster: 1. HPA can finally scale to zero (Beta, on by default) KEP-2021 - kubernetes/enhancements/keps/sig-autoscaling/2021-scale-from-zero This one has been around since 1.16 behind the HPAScaleToZero gate. In 1.37 it is Beta and enabled by default. You set minReplicas: 0 and the HPA is allowed to take the workload all the way down to zero, then bring it back when the metric moves again. The catch is in the metric type. It only works with Object or External metrics. CPU and memory metrics come from running Pods, so with zero Pods there is nothing to measure and nothing to wake up on. In practice this is for queue consumers, batch workers and GPU inference services that sit idle at night. apiVersion: autoscaling/v2 kind: HorizontalPodAutoscaler metadata: name: order-worker spec: scaleTargetRef: apiVersion: apps/v1 kind: Deployment name: order-worker minReplicas: 0 maxReplicas: 20 metrics: - type: External external: metric: name: queue_messages_ready selector: matchLabels: queue: orders target: type: AverageValue averageValue: "30" One detail I liked: while the HPA holds the workload at zero, it sets a ScaledToZero=True condition. That's how it tells "I parked this" apart from "a human set replicas to 0 on purpose"

## API Versioning Strategy When AI Agents Are Your Consumers

DevFeed: [API Versioning Strategy When AI Agents Are Your Consumers](<https://devfeed.tech/articles/api-versioning-strategy-when-ai-agents-are-your-consumers-92487.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/api-versioning-strategy-ai-agents>)

Author: Swytchcode Team

Published: 2026-10-21T09:53:12.592027Z

Content type: article

Language: en

Sources: [Swytchcode](<https://devfeed.tech/sources/swytchcode.md>)

Topics: [versioning](<https://devfeed.tech/topics/versioning.md>), [API](<https://devfeed.tech/topics/api.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-integration](<https://devfeed.tech/tags/agent-integration.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [changelog](<https://devfeed.tech/tags/changelog.md>), [consumer](<https://devfeed.tech/tags/consumer.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [strategy](<https://devfeed.tech/tags/strategy.md>), [v1](<https://devfeed.tech/tags/v1.md>), [versioning](<https://devfeed.tech/tags/versioning.md>)

### AI overview

Agent callers may keep using the API shape they were built against, so deprecation notices alone may not prevent production breakage. The excerpt highlights schema drift within a still-current version--such as a field becoming required, a default changing, or tighter rate limits--as a key risk; some mismatches may silently drop expected data. It recommends validating each call against the live schema, failing with a specific error on mismatch, and monitoring agent traffic during deprecation windows. It describes Swytchcode's execution pipeline as checking the real provider schema before a call runs. Detecting deprecated-version use also requires logging versions and endpoints and reviewing that traffic. The excerpt does not compare versioning approaches in depth.

### Source excerpt

A human reads the changelog. An agent keeps calling v1 until it 404s. What a versioning strategy needs to look like when the consumer never checks release notes.

## Governing your lakehouse with Fivetran Managed Data Lake Service | Blog | Fivetran

DevFeed: [Governing your lakehouse with Fivetran Managed Data Lake Service | Blog | Fivetran](<https://devfeed.tech/articles/governing-your-lakehouse-with-fivetran-managed-data-lake-service-blog-fivetran-136781.md>)

Original publisher: [Read original article](<https://wf.fivetran.com/blog/governing-your-lakehouse-with-fivetran-managed-data-lake-service>)

Author: Andrew Madson

Published: 2026-10-13T16:41:32Z

Content type: article

Language: en

Sources: [Fivetran Blog](<https://devfeed.tech/sources/fivetran-blog.md>)

Topics: [Data Management](<https://devfeed.tech/topics/data-management.md>), [data lake](<https://devfeed.tech/topics/data-lake.md>), [data ownership](<https://devfeed.tech/topics/data-ownership.md>), [data-architecture](<https://devfeed.tech/topics/data-architecture.md>), [AWS Glue](<https://devfeed.tech/topics/aws-glue.md>), [Data Infrastructure](<https://devfeed.tech/topics/data-infrastructure.md>), [Security, Identity, & Compliance](<https://devfeed.tech/topics/security-identity-compliance.md>), [AWS Lake Formation](<https://devfeed.tech/topics/aws-lake-formation.md>), [deltalake](<https://devfeed.tech/topics/deltalake.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>), [data-processing](<https://devfeed.tech/topics/data-processing.md>), [Amazon Redshift](<https://devfeed.tech/topics/amazon-redshift.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [apache-polaris](<https://devfeed.tech/tags/apache-polaris.md>), [athena](<https://devfeed.tech/tags/athena.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [automated](<https://devfeed.tech/tags/automated.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-glue](<https://devfeed.tech/tags/aws-glue.md>), [aws-privatelink](<https://devfeed.tech/tags/aws-privatelink.md>), [azure](<https://devfeed.tech/tags/azure.md>), [biglake](<https://devfeed.tech/tags/biglake.md>), [bigquery](<https://devfeed.tech/tags/bigquery.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [data](<https://devfeed.tech/tags/data.md>), [data-lake](<https://devfeed.tech/tags/data-lake.md>), [fivetran](<https://devfeed.tech/tags/fivetran.md>), [governance](<https://devfeed.tech/tags/governance.md>), [lakehouse](<https://devfeed.tech/tags/lakehouse.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>)

### AI overview

The excerpt presents Fivetran Managed Data Lake governance as a single-source-of-truth model: Fivetran alone writes Iceberg metadata, while query engines read it, and Fivetran republishes the correct version if AWS Glue drifts. Engines can use the Iceberg REST Catalog with OAuth2; Athena and Redshift require Glue integration enabled at destination setup, a permanent choice with regional and naming constraints. Access controls include short-lived, table-scoped S3 credentials, cross-account IAM, and optional KMS, Lake Formation, and Business Critical PrivateLink configuration. Automated retention, metadata version cleanup, biweekly orphan-file removal, compaction, deduplication, and schema evolution address lifecycle work. The excerpt warns against manual catalog changes and raw Parquet queries, and notes cloud-specific catalog requirements, including BigQuery Admin access for GCS BigLake.

### Source excerpt

Lakehouse governance requires observability, access control, data lifecycle management, and more. Fivetran MDLS makes it easy.

## Declarative Schemas 2.0 with pg-delta

DevFeed: [Declarative Schemas 2.0 with pg-delta](<https://devfeed.tech/articles/declarative-schemas-2-0-with-pg-delta-86232.md>)

Original publisher: [Read original article](<https://supabase.com/blog/declarative-schemas-2-0-pg-delta>)

Author: Andrew Valleteau; Wen Bo Xie

Published: 2026-10-13T07:00:00Z

Content type: release

Language: en

Sources: [Supabase](<https://devfeed.tech/sources/supabase-blog.md>)

Topics: [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [cli](<https://devfeed.tech/tags/cli.md>), [database](<https://devfeed.tech/tags/database.md>), [database-schema](<https://devfeed.tech/tags/database-schema.md>), [migrations](<https://devfeed.tech/tags/migrations.md>)

### AI overview

Supabase Declarative Schemas 2.0 replaces migra with pg-delta, a PostgreSQL diff tool that generates migrations from SQL schema files. The release adds coverage for objects including row-level security policies, grants, view settings, partitions and domains, and explains setup, migration review and current limitations. pg-delta is in alpha, and generated changes may require manual edits, especially when a column rename appears as a drop and add.

### Source excerpt

The migrations the CLI writes for you no longer skip RLS policy changes, grants, view settings, partitions, or domains.

## Automating Data Ingestion with a RAG Flywheel

DevFeed: [Automating Data Ingestion with a RAG Flywheel](<https://devfeed.tech/articles/automating-data-ingestion-with-a-rag-flywheel-85490.md>)

Original publisher: [Read original article](<https://engineering.zalando.com/posts/2026/10/structure-automating-data-ingestion-with-a-rag-flywheel.html>)

Author: Tushar Gupta

Published: 2026-10-11T22:00:00Z

Content type: article

Language: en

Sources: [Zalando](<https://devfeed.tech/sources/zalando-engineering-blog.md>)

Topics: [Structured-data](<https://devfeed.tech/topics/structured-data.md>), [Amazon Bedrock Knowledge Bases](<https://devfeed.tech/topics/amazon-bedrock-knowledge-bases.md>), [etcd](<https://devfeed.tech/topics/etcd.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Embeddings](<https://devfeed.tech/topics/embeddings.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [amazon-titan](<https://devfeed.tech/tags/amazon-titan.md>), [anthropic-claude](<https://devfeed.tech/tags/anthropic-claude.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-bedrock](<https://devfeed.tech/tags/aws-bedrock.md>), [backend](<https://devfeed.tech/tags/backend.md>), [better](<https://devfeed.tech/tags/better.md>), [data-ingestion](<https://devfeed.tech/tags/data-ingestion.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llms](<https://devfeed.tech/tags/llms.md>), [machine-learning](<https://devfeed.tech/tags/machine-learning.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [rag](<https://devfeed.tech/tags/rag.md>), [schema](<https://devfeed.tech/tags/schema.md>), [zalando](<https://devfeed.tech/tags/zalando.md>)

### AI overview

Zalando describes an LLM-assisted system for mapping varied supplier data columns to an internal schema. It combines embeddings, historical human-approved mappings retrieved with pgvector, and constrained model outputs with API validation and human review. The article reports that operations specialists accept 85% of suggestions without changes, while noting this is an operational signal rather than a formal accuracy benchmark.

### Source excerpt

Automating schema mapping for diverse supplier data using a RAG Flywheel and LLMs.

## Kafka Inconsistencies and the Silent Failures Behind Real-Time Decision Platforms

DevFeed: [Kafka Inconsistencies and the Silent Failures Behind Real-Time Decision Platforms](<https://devfeed.tech/articles/kafka-inconsistencies-and-the-silent-failures-behind-real-time-decision-platforms-62148.md>)

Original publisher: [Read original article](<https://medium.com/walmartglobaltech/kafka-inconsistencies-and-the-silent-failures-behind-real-time-decision-platforms-f6db55156286?source=rss----905ea2b3d4d1---4>)

Author: Pranav patil

Published: 2026-09-30T00:21:42Z

Content type: article

Language: en

Sources: [Walmart Global Tech](<https://devfeed.tech/sources/walmart-global-tech.md>)

Topics: [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [Event-Streaming](<https://devfeed.tech/topics/event-streaming.md>), [streaming data analytics](<https://devfeed.tech/topics/streaming-data-analytics.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>)

Tags: [broker](<https://devfeed.tech/tags/broker.md>), [consumer](<https://devfeed.tech/tags/consumer.md>), [data-engineering](<https://devfeed.tech/tags/data-engineering.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [detection](<https://devfeed.tech/tags/detection.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [event-streaming](<https://devfeed.tech/tags/event-streaming.md>), [events](<https://devfeed.tech/tags/events.md>), [failure](<https://devfeed.tech/tags/failure.md>), [groups](<https://devfeed.tech/tags/groups.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [lag](<https://devfeed.tech/tags/lag.md>), [partitions](<https://devfeed.tech/tags/partitions.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [pods](<https://devfeed.tech/tags/pods.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [risk](<https://devfeed.tech/tags/risk.md>), [semantics](<https://devfeed.tech/tags/semantics.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [state](<https://devfeed.tech/tags/state.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [system-design-interview](<https://devfeed.tech/tags/system-design-interview.md>), [time](<https://devfeed.tech/tags/time.md>)

### AI overview

Kafka-backed decision systems can look healthy while making wrong decisions because of duplicates, late or out-of-order events, stale state, silent data loss, or mixed consumer versions. The illustrative incident centers on a rolling deployment where old and new pods share a consumer group, so partitions may be handled under different logic. The article recommends separating code rollout from behavior changes with feature flags, or using versioned or blue/green consumer groups for semantic changes, while choosing replay offsets deliberately. It also advises stable entity partition keys, consumer-side idempotency, event-time handling and correction policies, freshness monitoring, end-to-end reconciliation, and alerting on DLQ growth. Producer, topic, and consumer settings can bound failures but are not sufficient alone; for example, disabling auto-commit helps only when offsets follow successful processing and side effects. The incident is an illustrative composite, not a report of a specific production event.

### Source excerpt

A field guide to the duplicate events, stale state, rebalances, and deployment traps that quietly distort real-time decisions -- told through one decision that should have fired and didn't. Note: This piece assumes working familiarity with Kafka and event-streaming fundamentals -- topics, partitions, offsets, consumer groups, and delivery semantics. Terms are expanded on first use where it helps, but the focus is on how these behaviors affect real-time decisions, not on introducing Kafka itself. The scenario, systems, and incident described throughout are an illustrative composite created for this article -- they do not describe, and are not traceable to, any specific organization, production system, or real-world event.The failure that doesn't alert you Some failures announce themselves. A broker goes down, a consumer crashes, lag spikes, an alert goes off, someone starts a bridge call. Those are the easy ones. This is about the other kind. Picture a real-time risk detection system doing its job: consuming events, scoring them, taking action. Dashboards green. Consumer lag normal. No pods restarting. No alerts. By every signal a team usually trusts, the system is healthy. And yet, somewhere in that healthy-looking pipeline, a decision that should have fired didn't. An action the system was built to catch went through anyway. Nothing crashed. Nothing logged an error. The pipeline reported itself perfectly fine the entire time. That is the uncomfortable truth about Kafka in real-time decision systems: the scariest failures aren't the ones that page you. They're the ones that let the system look healthy while a decision quietly goes wrong. This article walks through one such illustrative case -- what the symptom looks like, the family of quiet failures that could produce it, the one that actually does, and how it gets fixed. Along the way, every Kafka concept you need to reason about real-time pipelines shows up where it naturally belongs: as a possible explanation for a

## Building a Data Lakehouse with DuckDB and DuckLake

DevFeed: [Building a Data Lakehouse with DuckDB and DuckLake](<https://devfeed.tech/articles/building-a-data-lakehouse-with-duckdb-and-ducklake-56876.md>)

Original publisher: [Read original article](<https://towardsdatascience.com/building-a-data-lakehouse-with-duckdb-and-ducklake/>)

Author: Thomas Reid

Published: 2026-09-17T15:30:02Z

Content type: tutorial

Language: en

Sources: [Towards Data Science](<https://devfeed.tech/sources/towards-data-science.md>)

Topics: [DuckDB](<https://devfeed.tech/topics/duckdb.md>), [data lake](<https://devfeed.tech/topics/data-lake.md>), [parquet](<https://devfeed.tech/topics/parquet.md>), [Database](<https://devfeed.tech/topics/database.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [cloud](<https://devfeed.tech/tags/cloud.md>), [data](<https://devfeed.tech/tags/data.md>), [data-engineering](<https://devfeed.tech/tags/data-engineering.md>), [data-lake](<https://devfeed.tech/tags/data-lake.md>), [data-lakehouse](<https://devfeed.tech/tags/data-lakehouse.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [duckdb](<https://devfeed.tech/tags/duckdb.md>), [evolution](<https://devfeed.tech/tags/evolution.md>), [lakehouse](<https://devfeed.tech/tags/lakehouse.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [parquet](<https://devfeed.tech/tags/parquet.md>)

### AI overview

A tutorial on building a low-cost data lakehouse with DuckDB and the DuckLake extension. It explains the evolution from databases and data warehouses to data lakes, then covers Parquet files, metadata, transactions, schema evolution, and time travel.

### Source excerpt

Starting with a local Parquet file, then joining it to data stored in the cloud The post Building a Data Lakehouse with DuckDB and DuckLake appeared first on Towards Data Science.

## Data Lakehouse vs Medallion Architecture: Not the Comparison You Think

DevFeed: [Data Lakehouse vs Medallion Architecture: Not the Comparison You Think](<https://devfeed.tech/articles/data-lakehouse-vs-medallion-architecture-not-the-comparison-you-think-51555.md>)

Original publisher: [Read original article](<https://www.dremio.com/blog/data-lakehouse-vs-medallion-architecture/>)

Author: Alex Merced

Published: 2026-09-10T23:36:24Z

Content type: article

Language: en

Sources: [Dremio](<https://devfeed.tech/sources/dremio.md>)

Topics: [data](<https://devfeed.tech/topics/data.md>), [Apache Iceberg](<https://devfeed.tech/topics/apache-iceberg.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [parquet](<https://devfeed.tech/topics/parquet.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>)

Tags: [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [data-lakehouse](<https://devfeed.tech/tags/data-lakehouse.md>), [dremio-blog-various-insights](<https://devfeed.tech/tags/dremio-blog-various-insights.md>), [lakehouse](<https://devfeed.tech/tags/lakehouse.md>), [object-storage](<https://devfeed.tech/tags/object-storage.md>), [parquet](<https://devfeed.tech/tags/parquet.md>), [schema-evolution](<https://devfeed.tech/tags/schema-evolution.md>), [storage](<https://devfeed.tech/tags/storage.md>), [table](<https://devfeed.tech/tags/table.md>)

### AI overview

The article explains that a data lakehouse and medallion architecture are complementary rather than competing choices. A lakehouse defines platform components such as object storage, an open table format, a catalog, and query engines, while medallion architecture organizes data into bronze, silver, and gold layers. It argues that the key cost decision is how many physical data copies those layers require.

### Source excerpt

These are not competing choices. One describes what your platform is made of, the other describes how you organise tables inside it. The costly decision is the copy count. The post Data Lakehouse vs Medallion Architecture: Not the Comparison You Think appeared first on Dremio.

## Introducing WalShadow: Sub-second Postgres replication to ClickHouse from physical WAL

DevFeed: [Introducing WalShadow: Sub-second Postgres replication to ClickHouse from physical WAL](<https://devfeed.tech/articles/introducing-walshadow-sub-second-postgres-replication-to-clickhouse-from-physical-wal-5344.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/introducing-walshadow>)

Author: Sai Srirampur

Published: 2026-09-10T15:53:42Z

Content type: article

Language: en

Sources: [ClickHouse Blog](<https://devfeed.tech/sources/clickhouse-blog.md>)

Topics: [clickhouse](<https://devfeed.tech/topics/clickhouse.md>), [Database](<https://devfeed.tech/topics/database.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>), [Latency](<https://devfeed.tech/topics/latency.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [github](<https://devfeed.tech/tags/github.md>), [latency](<https://devfeed.tech/tags/latency.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [replication](<https://devfeed.tech/tags/replication.md>), [schema-evolution](<https://devfeed.tech/tags/schema-evolution.md>), [transactions](<https://devfeed.tech/tags/transactions.md>)

### AI overview

WalShadow is an open-source engine that replicates PostgreSQL data to ClickHouse from the physical WAL stream. The article describes benchmark results of about 200 ms visibility latency and 289K rows per second, plus support for initial loads, continuous replication, schema evolution, recovery, and source switchovers.

### Source excerpt

WalShadow replicates Postgres data directly from physical WAL into ClickHouse, delivering around 200 ms latency and 289,000 rows per second in benchmarks.

## Build a dynamic streaming data lake with Apache Iceberg and Apache Flink

DevFeed: [Build a dynamic streaming data lake with Apache Iceberg and Apache Flink](<https://devfeed.tech/articles/build-a-dynamic-streaming-data-lake-with-apache-iceberg-and-apache-flink-49909.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/build-a-dynamic-streaming-data-lake-with-apache-iceberg-and-apache-flink/>)

Author: Francisco Morillo

Published: 2026-09-02T18:28:38Z

Content type: tutorial

Language: en

Sources: [AWS Big Data Blog](<https://devfeed.tech/sources/aws-big-data-blog.md>)

Topics: [Apache Flink](<https://devfeed.tech/topics/apache-flink.md>), [Apache Iceberg](<https://devfeed.tech/topics/apache-iceberg.md>), [data lake](<https://devfeed.tech/topics/data-lake.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-managed-service-for-apache-flink](<https://devfeed.tech/tags/amazon-managed-service-for-apache-flink.md>), [apache-flink](<https://devfeed.tech/tags/apache-flink.md>), [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [aws](<https://devfeed.tech/tags/aws.md>), [data-lake](<https://devfeed.tech/tags/data-lake.md>), [data-pipelines](<https://devfeed.tech/tags/data-pipelines.md>), [kinesis-data-streams](<https://devfeed.tech/tags/kinesis-data-streams.md>), [schema-evolution](<https://devfeed.tech/tags/schema-evolution.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

This tutorial explains how to build a streaming data lake on Amazon Managed Service for Apache Flink using Apache Iceberg's Dynamic Iceberg Sink. The approach routes records to Iceberg tables and handles new event types and schema changes without stopping the pipeline.

### Source excerpt

Learn how to build a dynamic streaming data lake on Amazon Managed Service for Apache Flink that adapts to new event types and schema changes without stopping the pipeline, using Apache Iceberg's Dynamic Iceberg Sink for per-record table routing and automatic schema evolution.

[Next page](<https://devfeed.tech/topics/schema-evolution.md?cursor=WyIyMDI2LTA5LTAyVDE4OjI4OjM4KzAwOjAwIiwgIjhkNGFhZDlhLWI1ZTUtNGNjNy05ZTYzLTljM2U4MWQ0MTNiMSJd>)