Closed dRuEFFECT closed 3 years ago
Hi @dRuEFFECT, thanks for your contribution!
In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes.
You did it @dRuEFFECT!
Thank you for signing the Singer Contribution License Agreement.
According to the Kustomer docs the pageSize limit is max 100
https://dev.kustomer.com/v1/customers/customer-search
How do you expect setting it to a value higher than 100 to behave?
ref: #12
For both PR https://github.com/singer-io/tap-kustomer/pull/13 and https://github.com/singer-io/tap-kustomer/pull/15 we're happy to merge it, but looking at the long discussion on the referenced issue https://github.com/singer-io/tap-kustomer/issues/12 I'm not convinced this will solve the root cause. I will work on merging them and then try to provide guidance on what I believe will better address the root cause (based on the information discussed).
I've pushed a local branch to trigger circle to run on this one.
Looks like circle was broken due to some known python version and dependency compatibility issues, so I'm going to create a PR to fix circle.
Now that the circle fix is merged I'm going to hit the button to update the branch.
Pushing the local branch again to trigger circle
The build is green, merging it. I'll proceed to do something similar for the other PR. After that I'll comment on the github issue of what I really suspect is the root cause.
page_size_limit is supposed to be user configurable in order to account for hundreds of rows with the exact same updated timestamp. In Stitch, this is not available in the GUI and the integration runs with a fixed page_size_limit value of 100, causing pagination issues. comments in the sync.py script say this should be at least 300.
I don't assume this example file will directly affect the Stitch GUI, but the example file should include it at least.
Description of change
added page_size_limit
QA steps
(I don't know what to add here)
Risks
Rollback steps