-
Notifications
You must be signed in to change notification settings - Fork 4.6k
refactor[source-snapchat-marketing]: migrate to low-code #39507
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor[source-snapchat-marketing]: migrate to low-code #39507
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
…ode' of github.com:airbytehq/airbyte into lazebnyi/8283-source-snapchat-marketing-migrate-to-lowcode
…ode' of github.com:airbytehq/airbyte into lazebnyi/8283-source-snapchat-marketing-migrate-to-lowcode
...te-integrations/connectors/source-snapchat-marketing/source_snapchat_marketing/components.py
Outdated
Show resolved
Hide resolved
...te-integrations/connectors/source-snapchat-marketing/source_snapchat_marketing/components.py
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lazebnyi do you know why the acceptance test is failing? The failure is different than the one I see on the nightly build
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good!
Co-authored-by: Alexandre Girard <[email protected]>
airbyte-integrations/connectors/source-snapchat-marketing/metadata.yaml
Outdated
Show resolved
Hide resolved
Co-authored-by: Alexandre Girard <[email protected]>
What
Resolves https://github.com/airbytehq/airbyte-internal-issues/issues/8283
How
We have migrated streams to a low-code platform. However, the analytics streams remain in Python, as the low-code implementation requires custom logic for slicing, parsing records, and mapping records that were sliced into fields by chunks.
Review guide
manifest.yaml
source.py
User Impact
Format of state has changed for all connectors as they use per partition state
Can this PR be safely reverted and rolled back?