-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
🎉 New Source Braze: new source implemented in low-code #20520
Conversation
fa4a8de
to
409dd74
Compare
/test connector=connectors/source-braze
Build PassedTest summary info:
|
|
||
|
||
@dataclass | ||
class DatetimeStreamSlicerComponent(DatetimeStreamSlicer): |
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.
can you create an issue requesting that this is added to the datetimestreamslicer like described here and clarifying what the new component should do, and add the issue to the docstring?
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.
I don't understand why this is different than the datetimestreamslicer. Can you clarify in the docstring? doesn't datetime stream slicer already have step size?
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.
Step exists in basic DatetimeStreamSlicer
but I need it to be an option which will be passed as a request parameter and to be calculated based on difference between start/end dates. I need the step amount to be more than actual size of the difference by 1, but not for fist slice. I also do not need last slice if start/end dates are equal. And it is important thing that step amount is dynamic because last slice must not be equal to the step amount if the difference between start/end dates lesser than in step. All of this is not a standard thing and I am not sure we need it in DatetimeStreamSlicer
.
Why I need it:
Braze API provides us with ending_at
and length
query params, so we can to specify latest point and then move back by length
until reach start_date
(initially specified by user), which is ignored by API (even if we specify starting_at
we still getting records older than starting_at
, if step
is bigger than difference of ending_at
- starting_at
. And starting_at
is available for only few endponts). Date specified in ending_at
is an exclusive property which means we are getting length
records strictly less than ending_at
, but DatetimeStreamSlicer
adds 1 day to previous end date to calculate next start date for next slice, that is why we loose 1 record between each slice. Having step
query parameter amount one higher than actual difference lets us avoid the problem with gaps in slice windows
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.
LGTM for this PR but please create two github issues to track the custom components in this PR
|
||
|
||
@dataclass | ||
class TransformToRecordComponent(AddFields): |
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.
please create a Github issue for this custom component as well so we can keep track of which components we need to add to the CDK
/publish connector=connectors/source-braze
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/source-braze
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/source-braze
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/source-braze
if you have connectors that successfully published but failed definition generation, follow step 4 here |
Thank you for this connector, very much appreciated! |
What
New Braze connector
How
Low-code connector
Recommended reading order
braze.yaml
y.python