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

Found a difference between data arriving in Snowflake/Bigquery vs Postgres #34

Open
FlorianDeliverect opened this issue Nov 14, 2020 · 1 comment

Comments

@FlorianDeliverect
Copy link

Hi,

I was migrating to Snowflake from a Postgres-based analytics set-up and found a difference.
The Postgres one is correct after checking in chargebee.
I thought this might be a Snowflake error so I created another stitch account and sent my data to Bigquery.
However there I have exactly the same data as in Snowflake.

I'm talking about the customer-table. I don't know how often it happens, but here is an example record for which I made a field by field comparison : https://docs.google.com/spreadsheets/d/19pjWtwEjfOY8s0gJdVEa1gBwopclo8CI68xJpURX_xM/edit#gid=0

Strangely for Snowflake/Bigquery the updated_at field equals the created_at field while that customer has received many changes since it's creation date. All fields seem to correspond with the state they had at creation time while in postgres the updated_at field is this month and the other fields match what I find in Chargebee. Another strange thing is that the field DELETED is set to TRUE in the Snowflake/Bigquery version, while I cannot find any customer_deleted event in the customer's event history.

If you have any idea what's wrong, let me know.

Florian

@cb-nandita
Copy link

@FlorianDeliverect ,
Hope you are doing well.
Could you please check and confirm if there are any errors in the Stitch logs? Are all the syncs successful ?

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