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

Source Amplitude: events not syncing properly #10220

Closed
Tracked by #12240
dermasmid opened this issue Feb 9, 2022 · 1 comment · Fixed by #12430
Closed
Tracked by #12240

Source Amplitude: events not syncing properly #10220

dermasmid opened this issue Feb 9, 2022 · 1 comment · Fixed by #12430
Assignees
Labels
area/connectors Connector related issues autoteam community connectors/source/amplitude team/tse Technical Support Engineers type/bug Something isn't working

Comments

@dermasmid
Copy link

dermasmid commented Feb 9, 2022

Environment

  • Airbyte version: 0.35.26-alpha
  • OS Version / Instance: debian 10
  • Deployment: docker
  • Source Connector and version: Amplitude 0.1.4
  • Destination Connector and version: postgres
  • Severity: High
  • Step where error happened: Sync job

Current Behavior

amplitude returns a 404 if the time range that we are trying to pull doesn't have any data, and the connector doesnt handle it and just quits.

Expected Behavior

the connector should try the next dates until it doesnt get a 404.

Logs

logs-1.txt

LOG
2022-02-09 13:19:32 source > Syncing stream: events 
2022-02-09 13:19:35 source > Error during syncing events stream - 404 Client Error: Not Found for url: https://amplitude.com/api/2/export?start=20210601T00&end=20210604T00
2022-02-09 13:19:35 source > Setting state of events stream to {}
2022-02-09 13:19:35 source > Read 0 records from events stream
2022-02-09 13:19:35 source > Finished syncing SourceAmplitude
2022-02-09 13:19:35 source > SourceAmplitude runtimes:
2022-02-09 13:19:35 source > Finished syncing SourceAmplitude
2022-02-09 13:19:36 INFO i.a.w.DefaultReplicationWorker(run):162 - One of source or destination thread complete. Waiting on the other.
2022-02-09 13:19:36 destination > 2022-02-09 13:19:36 INFO i.a.i.b.FailureTrackingAirbyteMessageConsumer(close):60 - {} - Airbyte message consumer: succeeded.
2022-02-09 13:19:36 destination > 2022-02-09 13:19:36 INFO i.a.i.d.b.BufferedStreamConsumer(close):200 - {} - executing on success close procedure.
2022-02-09 13:19:36 destination > 2022-02-09 13:19:36 INFO i.a.i.d.j.JdbcBufferedConsumerFactory(lambda$onCloseFunction$3):160 - {} - Finalizing tables in destination started for 4 streams

Steps to Reproduce

1.create amplitude source with start date before the account was created
2.try to sync events

Are you willing to submit a PR?

yes

@dermasmid
Copy link
Author

Related to #6375 and #6541.
Why this is still a bug - sometimes you dont know the exact date that you started to have data in amplitude, so the connector should be able to handle that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connectors Connector related issues autoteam community connectors/source/amplitude team/tse Technical Support Engineers type/bug Something isn't working
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

6 participants