jan_soubusta
03/08/2023, 5:07 PMvisch
03/08/2023, 5:08 PMjan_soubusta
03/08/2023, 5:13 PMjan_soubusta
03/08/2023, 5:17 PMpat_nadolny
03/08/2023, 5:23 PMjan_soubusta
03/08/2023, 5:26 PMaaronsteers
03/08/2023, 6:14 PMaaronsteers
03/08/2023, 6:15 PMaaronsteers
03/08/2023, 6:17 PMpat_nadolny
03/08/2023, 7:05 PMpat_nadolny
03/08/2023, 10:22 PMStéphane Burwash
03/09/2023, 1:19 PMjan_soubusta
03/09/2023, 4:31 PMdanylo
03/09/2023, 6:24 PMStart Date (start_date)
, and if so for which streams?Stéphane Burwash
03/09/2023, 7:36 PMjan_soubusta
03/14/2023, 11:00 AM- name: tap-hubspot
variant: potloc
pip_url: git+<https://github.com/potloc/tap-hubspot.git>
capabilities:
- schema-flattening
- state
- catalog
- discover
select:
- contacts.*
Execution fails:
meltano run tap-hubspot target-snowflake
2023-03-14T10:57:20.674429Z [info ] raise FatalAPIError(msg) cmd_type=elb consumer=False name=tap-hubspot producer=True stdio=stderr string_id=tap-hubspot
2023-03-14T10:57:20.674648Z [info ] singer_sdk.exceptions.FatalAPIError: 414 Client Error: URI Too Long for path: /crm/v3/objects/contacts cmd_type=elb consumer=False name=tap-hubspot producer=True stdio=stderr string_id=tap-hubspot
2
Any advice?Stéphane Burwash
03/14/2023, 1:14 PM_LOG_REQUEST_METRICS_URL
variable?
This is a problem on the hubspot side where we are specifying too many properties in the URI. There would be 2 solutions to this:
• 1 - create an option to specify if you want "barebones" or "all properties" for specific endpoints from the tap, and then depending on that variable see if we get our results from a static schema or a dynamic one where we get all the properties
• 2 - Use the "search" API to introduce the URI parameters in the body, removing the problem altogether.
I'll try to dig into this a bit more though 😄jan_soubusta
03/14/2023, 2:06 PMStéphane Burwash
03/14/2023, 2:12 PM_LOG_REQUEST_METRICS_URL
in a specific stream, which allows you to view the message being sent out to the API. This would allow you to see what data is being sent out and help us debug your issue.
To do this, simply fork my repo and add the line _LOG_REQUEST_METRICS_URL=true
here. This log output should then be more helpful.
Regarding the 2 solutions, I'll do a bit of research on my end and reach back out this afternoon; I just want to validate a few things first 😄.Stéphane Burwash
03/14/2023, 9:13 PMjan_soubusta
03/15/2023, 12:02 PM_LOG_REQUEST_METRICS_URL=true
and send you the results.sarah_krasnik
05/02/2023, 6:11 PMStéphane Burwash
05/02/2023, 7:37 PMsweta_garai
05/03/2023, 6:19 PM