Joshua Garza
12/03/2025, 4:54 AMkapa.ai
12/03/2025, 4:54 AMStatsAggregationHelper.hydrateWithStats / getConnectionLastJobPerStream). It’s the same type of problem as other duplicate‑key issues we’ve seen (e.g., duplicate keys in DB constraints or config maps), but there is no specific mention of this exact StatsAggregationHelper error pattern in the available knowledge sources. What we do know from the docs/issues you shared: - Airbyte has several duplicate‑key style bugs reported in 1.8.x, e.g. the pk_connector_rollout constraint violation during the cron DefinitionsUpdater job, which is an open issue in 1.8.0/1.8.1 and requires a product fix rather than configuration changes.[[1.8.0/1.8.1 rollout](https://github.com/airbytehq/airbyte/issues/65134)] - Duplicate‑key situations can also surface at the configuration/metadata level (e.g. Helm chart ConfigMap duplicate keys, “duplicate key” errors for actor catalog fetch events), and the recommended resolution in those cases has been to upgrade once a fix is released, or to adjust the problematic configuration.[[Helm ConfigMap dup](https://github.com/airbytehq/airbyte/issues/66546); [Actor catalog dup](https://discuss.airbyte.io/t/3750)] However, none of the sources describe: - A known bug specifically in StatsAggregationHelper.hydrateWithStats or getConnectionLastJobPerStream, or - A documented workaround for this exact Duplicate key 54 error on full‑refresh‑overwrite jobs. Because of that, I cannot confidently tell you: - Whether this is already tracked as a specific GitHub issue, or - Whether a particular Airbyte version definitively fixes it. Given the constraints of the available information, the best I can suggest (without guessing) is: 1. Treat this as a likely product bug similar to the other duplicate‑key cases. 2. Check whether you’re on an older minor/patch version (e.g., around 1.8.x) and, if feasible, upgrade to the latest stable Airbyte version, since recent duplicate‑key problems have been addressed via upgrades in the past.[[1.8.0/1.8.1 rollout](https://github.com/airbytehq/airbyte/issues/65134)] 3. If the error persists on the latest version, open or update a GitHub issue including: - This full stack trace - Airbyte version and deployment type - Connection ID and job IDs involved - Confirmation that it occurs on a simple full‑refresh‑overwrite connection I’m sorry I can’t be more specific; the current knowledge sources simply do not describe this exact failure mode in enough detail to give a targeted fix.Joshua Garza
12/03/2025, 5:00 AMJoshua Garza
12/03/2025, 5:00 AM