-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
[ISSUE #20771] adding slices to connector builder read request #21605
[ISSUE #20771] adding slices to connector builder read request #21605
Conversation
I need to test this - I think there is some code in there to handle multiple slices but as you noted it's not used at the moment. But it's not blocking for this PR, we can also fix it as a follow-up. |
…issue-20771_adding-slices-to-read-response
@girarda if you are interested |
There is no test that validates 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.
couple of questions that maybe span outside of the scope of the PR. lgtm 🚢
#21525) * [ISSUE #20771] limiting the number of requests performed to the backend without flag * [ISSUE #20771] code reviewing my own code * [ISSUE #20771] adding ABC to paginator * [ISSUE #20771] format code * [ISSUE #20771] adding slices to connector builder read request (#21605) * [ISSUE #20771] adding slices to connector builder read request * [ISSUE #20771] formatting * [ISSUE #20771] set flag when limit requests reached (#21619) * [ISSUE #20771] set flag when limit requests reached * [ISSUE #20771] assert proper value on test read objects __init__ * [ISSUE #20771] code review and fix edge case * [ISSUE #20771] fix flake8 error * [ISSUE #20771] code review * 🤖 Bump minor version of Airbyte CDK * to run the CI
What
In order to validate if the number of requests was limited, we want to be able to know how many pages and slices were queries. We already had the information for the pages but didn't for the slices. This PR addresses the slices part.
How
Emit a log message when a new slice is being started and catch this log message to create the slices properly
Recommended reading order
airbyte-cdk/python/airbyte_cdk/sources/abstract_source.py
: how the slice message is loggedairbyte-connector-builder-server/connector_builder/impl/default_api.py
: how we use this log message to create the slices on the connector-builder server🚨 User Impact 🚨
@flash1293, will this be supported by the UI? Although not a breaking API change, there were some assumptions in the backend that there will always be only one slice.