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

Stripe Source can't sync Customers on 0.29.9-alpha - Normalization Failed #5515

Closed
erichartono opened this issue Aug 19, 2021 · 3 comments
Closed

Comments

@erichartono
Copy link

Enviroment

  • Airbyte version: 0.29.9-alpha
  • Instance: AWS EC2
  • Deployment: Docker
  • Source Connector and version: Stripe 0.1.16
  • Destination Connector and version: Redshift 0.3.12
  • Severity: Critical
  • Step where error happened: Sync job

Current Behavior

I had a connection that could sync Stripe Customers data on 0.29.4-alpha version. After upgrading to 0.29.9-alpha, I can't sync Customers data anymore. All other objects are synced successfully.

I tried to create new EC2 instance and run the same scenario, and got the same result.

  • Database Error in model customers_cards
  • column table_alias._airbyte_nested_data does not exist
  • Normalization Failed

Expected Behavior

Strip Customers data should sync without issue

Logs

logs-1-0 (1).txt

Steps to Reproduce

  1. Install AirByte 0.29.9-alpha on new EC2 instance
  2. Setup connection from Stripe to Redshift with only Customers object to sync
  3. Run sync
@erichartono erichartono added the type/bug Something isn't working label Aug 19, 2021
@erichartono
Copy link
Author

I experimented to setup clean AirByte on new EC2 instance, running 0.29.4-alpha and normalization 0.1.38 on this scenario. It worked without a glitch. Hope this is helpful.

image

@marcosmarxm
Copy link
Member

thanks @erichartono #5467 is solving this issue.

@erichartono
Copy link
Author

Thanks @marcosmarxm.

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

No branches or pull requests

3 participants