Open magsaas opened 6 months ago
Thanks for reporting the issue @magsaas Younium is a community connector and it isn't in the current roadmap for improvements. If you want to contribute fixing the issue please reach me out in Slack so I can provide you instructions to make the contribution 🎖️
@ellipsis-dev please make a PR to implement a better stop condition.
At Airbyte, we seek to be clear about the project priorities and roadmap. This issue has not had any activity for 180 days, suggesting that it's not as critical as others. It's possible it has already been fixed. It is being marked as stale and will be closed in 20 days if there is no activity. To keep it open, please comment to let us know why it is important to you and if it is still reproducible on recent versions of Airbyte.
Connector Name
source-younium
Connector Version
0.2.0
What step the error happened?
During the sync
Relevant information
We use the Younium connector and the Bookings endpoint logic is failing for stop condition.
In our case, we have 700 bookings in Younium at the moment, which amounts to 7 pages, however the connector doesn't stop at 7 pages, which leads to the error.
Steps to reproduce using an API client like Postman:
https://api.younium.com/Bookings?PageSize=100&PageNumber=1
where there's at least 1 booking. => If it's not the last page, the answer contains the keynextPage
with the next page as value:=> If it's the last page, the answer contains the key
lastPage
pointing to the same url that was just requested, and no nextPage:https://api.younium.com/Bookings?PageSize=100&PageNumber=X
where X is a page you know doesn't exist (i.e. lastPage+1). => API replies with a 400 Bad Request: No Bookings Found.What I've looked into
In the manifest file, the part related to the retrieval of data:
I guess there's a bug in how the stop_condition is handled but I'm not able to locate the logic responsible for handling this.
Relevant log output
Contribute