Data & Analytics
Airbyte Azure Table discovery shows only PartitionKey: validate before sync
Investigate incomplete Azure Table schema discovery before accepting a successful but empty sync.
November 10, 2026
A sync can look configured while its source schema is already wrong. In Airbyte issue 91290, an Azure Table source at connector version 0.1.57 discovers table names but exposes only PartitionKey. A separate report from the same user says a first sync returns zero rows without an obvious error. Treat these as related observations, not a confirmed root cause.
Establish the source truth
Query a small known table directly with Azure tooling. Record entity count and example properties, including PartitionKey, RowKey and Timestamp. Microsoft's Table Storage documentation explains the two-part key; Azure tables can also carry varying application properties.
Compare that sample with Airbyte discovery output, the selected stream schema and emitted record count. A missing RowKey at discovery is a stronger diagnostic signal than a green connection test. Capture connector version, Airbyte version and one sanitized entity for a reproducible support ticket.
Gate the destination on evidence
Pause downstream models that assume the stream is complete. Test with one table and a known row set; compare source count, emitted records and destination count. If discovery and extraction differ, keep those symptoms separate in the ticket. Avoid refreshing or resetting a production connection blindly because it may change cursor state without fixing the connector.
Adovo’s view
A pipeline's contract begins at discovery. If the source's key and fields are invisible, the job's success status cannot certify the data. Make a known-record reconciliation the release gate for every new connector.
