- Is this your first time deploying Airbyte?: No
- OS Version / Instance: Kubernetes with airbyte image
- Memory / Disk:
- Deployment: Are you using Docker or Kubernetes deployment?
- Airbyte Version: 0.39.11
- Source name/version: Hubspot 0.1.68
- Destination name/version: GCS 0.2.6
- Step: During Sync
- Description: When syncing Hubspot with GCS I got the following error :
tech.allegro.schema.json2avro.converter.AvroConversionException: Failed to convert JSON to Avro: Could not evaluate union, field timestamp is expected to be one of these: NULL, LONG, STRING. If this is a complex type, check if offending field (path: timestamp) adheres to schema: 1654779932443
Don’t know how to solve it would be awesome to get some help thanks
You could try to use Json format? Avro/Parquet has limited options with complex schemas.
HI it works better with JSON format indeed.
However I still have an issue in k8s env it seems that temporal fails (is it possible to get the logs from temporal ?) With docker-compose in local it works pretty well
Update I increased the pod resource and now I have this error :
java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.lang.NullPointerException: Cannot invoke "com.fasterxml.jackson.databind.node.ObjectNode.put(String, String)" because "matchingSchema" is null
Any idea ?
The 143 error means OOM you need to increase resources for the connector. For k8s are you using Json format in destination too and same version as docker-compose?
Works fine with the last version of the schema. maybe a drift between version. Will close the thread
Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.