Summary
User reports an issue with number fields in a Salesforce to Postgres connection after migrating from self-hosted to cloud-hosted Airbyte, where number fields now include excessive decimal precision. The user seeks a solution to remove the extra precision.
Question
Hi, we are migrated our self hosted Airbyte to Cloud hosted and have found a discrepancy in our Number fields. This connection is a Salesforce source to a Postgres Destination, and every number field from the cloud now has .000000000 added to it. So original connection would have the final Postgres column be 662 but through cloud it ends up 662.000000000 . Our destination version for Postgres are very different, it was 0.4.0 and now is 2.0.12. Is there an easy way to remove all that extra precision?
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.