[ISSUE 48459] Source-Instagram: Remove Unsupported Fields in media_insights and user_insights #51011
+4
−71
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@nickzombolas is attempting to deploy a commit to the Airbyte Growth Team on Vercel. A member of the Team first needs to authorize it. |
|
|
nickzombolas
temporarily deployed
to
community-ci-auto
GitHub Actions
Inactive
nickzombolas
requested a deployment
to
community-ci
GitHub Actions
Waiting
nickzombolas
requested a deployment
to
community-ci
GitHub Actions
Waiting
nickzombolas
changed the title
|
Thanks for the quick update in this deprecation @nickzombolas |
|
I requested the team to review your contribution @nickzombolas |
marcosmarxm
requested changes
Jan 9, 2025
|
Thanks @nickzombolas the team is already working #51018 to get this fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Solves #48459
Starting January 8, 2025, the following fields are no longer supported in the following streams. Here are the Facebook docs as a reference: https://developers.facebook.com/docs/graph-api/changelog/version21.0
user_insights:
video_viewsuser_insights:
email_contacts, get_direction_clicks, profile_views, text_message_clicks, website_clicks, phone_call_clicksIncluding these fields results in a bad request and causes these streams to fail syncs.
How
Unsupported fields have been removed from requests. Schemas and ERDs have been updated
Review guide
Ensure All unsupported fields are removed from requests
User Impact
These metrics are no longer available, and will no longer be fetched in records. If users depend on these fields they will need to migrate away from them as Facebook will no longer provide them
Can this PR be safely reverted and rolled back?
Because rolling back this PR will produce bad requests and cause syncs to fail.