-
Notifications
You must be signed in to change notification settings - Fork 4.6k
✨Source Outreach: Migrate Python CDK to Low-code CDK #36602
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Awaiting review 😄 |
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.
leaving surface-level comments for now. Will report again after regression testing
) -> MutableMapping[str, Any]: | ||
params = {} | ||
if self.cursor_field in stream_state: | ||
params[f"filter[{self.cursor_field}]"] = stream_state[self.cursor_field] + "..inf" |
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.
could we use a standard DatetimeBasedCursor
and send requests with filter {{ stream_interval.start_time}}..{{ stream_interval.end_time }}
?
This might lead to submitting more requests in the case where there are very few records, but it would allow us to checkpoint between every interval which I see as a win here
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.
Could you please elaborate on the change, I am a little new to the stream_interval variable, Where could we retrieve that?
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.
if the query parameter is passed, the API is not responding as it should,
Showing error as Invalid DateTime given (2020-11-16T00:00:00.000000Z). DateTime filter parameters must be in the format \"YYYY-MM-DD\", \"YYYY-MM-DDTHH:MMZ\", \"YYYY-MM-DDTHH:MM:SSZ\", or \"YYYY-MM-DDTHH:MM:SS.UUUZ\"
Airbyte automatically converts stream_interval.start_time and stream_interval.end_time to cursor format, but backend is not recognizing it, so better to leave as CustomIncremental Sync as current is good I guess 😄
@@ -81,7 +81,7 @@ | |||
"creator": { | |||
"type": ["null", "array"], | |||
"items": { | |||
"type": "string" | |||
"type": ["string", "integer"] |
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.
let's flag this in the breaking change. I think this is important information because it means the field type in the destination and in downstream systems need to support both string and integer
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.
Done! Edited in metadata breaking change message
All comments resolved :) |
Marking PR as ready to merge |
Continued in #36954 |
What
Migrating Source Outreach to Low-Code CDK
Closes airbytehq/airbyte-internal-issues#6916
How
Developed using (Configuration Based Source) low-code CDK
Recommended reading order
spec.yaml
manifest.yaml
schemas/*
Tests
Integration & Acceptance
🚨 User Impact 🚨