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

TIMESTAMPS shown as null in schemas from Salesforce #4396

Closed
shmf opened this issue Jun 29, 2021 · 5 comments
Closed

TIMESTAMPS shown as null in schemas from Salesforce #4396

shmf opened this issue Jun 29, 2021 · 5 comments
Assignees

Comments

@shmf
Copy link
Contributor

shmf commented Jun 29, 2021

Expected Behavior

Schema for tables retrieved from Salesforces should show TIMESTAMPS

Current Behavior

Schema for tables retrieved from Salesforces show NULL
Screenshot 2021-06-28 at 19 15 32

Logs

n/a

Steps to Reproduce

  1. create a connection between SFDC (source) and CSV (target - any should work)
  2. retrieve the source schemas
  3. check data type for TIMESTAMP fields

Severity of the bug for you

Medium

Airbyte Version

0.26.2

Connector Version (if applicable)

0.2.3

Additional context

Local deployment on GCP Compute Engine.
It is quite a big problem when the target is parquet because the schema shows a NULL datatype leading to a failure.

@shmf shmf added the type/bug Something isn't working label Jun 29, 2021
@marcosmarxm marcosmarxm added the area/connectors Connector related issues label Jun 29, 2021
@marcosmarxm
Copy link
Member

When using Postgres as destination fields are transferred as STRING but when using Parquet format is breaking the sync.
@tuliren for your information

@tuliren tuliren self-assigned this Jun 29, 2021
@tuliren tuliren added this to the Core - 2021-07-14 milestone Jul 7, 2021
@sherifnada
Copy link
Contributor

@shmf could you upload the log file for this sync job?

@tuliren
Copy link
Contributor

tuliren commented Jul 7, 2021

The root cause is probably #4294.

@tuliren
Copy link
Contributor

tuliren commented Jul 7, 2021

@shmf, would you mind trying the latest version of the S3 connector 0.1.8? This problem is probably solved in that version. If not, the log file should help us further debug it. Specially it would be helpful to know what the schema is for ACH_Submit_Timestamp__c. Thank you~~

@tuliren
Copy link
Contributor

tuliren commented Jul 13, 2021

Should have been resolved by #4613.

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

5 participants