Skip to content
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 with finding #16

Open
bensaxe opened this issue Feb 22, 2019 · 2 comments
Open

issue with finding #16

bensaxe opened this issue Feb 22, 2019 · 2 comments

Comments

@bensaxe
Copy link

bensaxe commented Feb 22, 2019

It looks like the integration hasn't been storing a STATE value to use as a bookmark to start the next extraction job on a recent base load I started. Each extraction has been starting again from the historical start-date I configured.

The result is that my transaction data only populates up until January of 2017, but will continue to run 6-hour limited extractions on past replicated data.

To solve for this, I just reset my start date to later than the max updated_at field value. Let me know if I need to expound on this particular issue.

@KAllan357
Copy link
Contributor

Thanks @bensaxe. It might be that this tap should be writing a bookmark after each daily pass in sync_transactions. Do your logs show many instances of this line:

https://github.com/singer-io/tap-braintree/blob/master/tap_braintree/__init__.py#L173

I suspect we could write the bookmark against end each time that log pops out.

@bensaxe
Copy link
Author

bensaxe commented Feb 25, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants