Summary
User encountered a KeyError during schema discovery for Facebook Marketing source with ‘mmm’ breakdown, indicating a discrepancy between the source setup and schema definition.
Question
Hi all!
I tried to set up a new Facebook Marketing source with “Custom Insights” and the “Breakdowns” set to mmm
.
The source was saved successfully.
When setting up a connection, discovering the schema failed with error message: KeyError: 'mmm'
.
After digging in the code, I found that Facebook Marketing Source setup page is using the facebook_business
Python package, which contains mmm
as valid breakdown.
However the “ads_insights_breakdowns.json” schema (which I guess is used when discovering the schema) doesn’t have mmm
as a valid property.
- Is this the right place to make a change request to add
mmm
as a valid property? - Is it by design that the source setup screen and the schema discovery code are using different sources of truth to identify valid breakdowns?
Thanks!
Airbyte version: 0.63.4
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.