Source Hubspot: failed sync Request-URI Too Large for contact stream

Connector Questions & Issues
1

Is this your first time deploying Airbyte : No
OS Version / Instance : Linux/EC2 t2.large
Memory / Disk : 8Gb / 24Gb
Deployment : Docker
Airbyte Version : 0.26.2-alpha
Source name/version : hubspot 0.1.5 and hubspot 0.1.13 too
Destination name/version : redshift/0.3.9Hey good morning Airbyte! One of my team members notified me this morning that they “added some new columns” to their Hubspot contacts table. Since that time the job in airbyte has been succeeding with 0 bytes/no records in 1 min 30 seconds (before this time it would succeed with 8.16 GB/500k records in a little over 3 hours). I updated the schema and re ran it multiple times but it keeps doing the same thing. I tested another table and it ran just fine so I feel like the problem lies with something that changed in the contacts table.Edit: When comparing two jobs I noticed that the 0 bytes jobs are throwing an HTTPError exception

File "/usr/local/lib/python3.7/site-packages/requests/models.py", line 943,
in raise_for_status raise HTTPError(http_error_msg, response=self) 
requests.exceptions.HTTPError: 414 Client Error: Request-URI Too Large for url:
 https://api.hubapi.com/crm/v3/objects/contact?limit=100&

Is there a limit to how many columns can be imported?

2

Github issue Hubspot connector crashes due to URL being too long · Issue #3977 · airbytehq/airbyte · GitHub.
Look this is a problem with Hubspot API.

Right now the workaround is: remove the fields you don’t need in this stream and build a custom version of connector.