-
Notifications
You must be signed in to change notification settings - Fork 26
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
Comments
Thanks @bensaxe. It might be that this tap should be writing a bookmark after each daily pass in https://github.com/singer-io/tap-braintree/blob/master/tap_braintree/__init__.py#L173 I suspect we could write the bookmark against |
We are running into the same issue even after restting the start date to a
later date in January. Our connection has been left loading all weekend and
it has not loaded in any new records.
It looks like we have the bookmark:
[image: image.png]
…On Mon, Feb 25, 2019 at 8:25 AM Kyle Allan ***@***.***> wrote:
Thanks @bensaxe <https://github.com/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.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ark72VSTzXwBumwIZ_BxqnC9lz_KkKt7ks5vQ-Q0gaJpZM4bLAPy>
.
--
____
*Benjamin Saxe*Finance & Operations Analyst
*Huckberry.com* <http://huckberry.com/>
[image: Instagram] <https://instagram.com/huckberry> [image: Facebook]
<https://facebook.com/huckberry>[image: Twitter]
<https://twitter.com/Huckberry>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: