Data factory Hubspot connector returns "414 Request-URI Too Large" on some endpoint(s)

Jesse Mikkola 1 Reputation point
2020-11-16T09:15:52.403+00:00

Hey,

we started getting an error with Data factory utilizing the Hubspot connector.
"
Operation on target Copy_7eo failed: Failure happened on 'Source' side. ErrorCode=UserErrorOdbcOperationFailed,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=ERROR [HY000] [Microsoft][Hubspot] (100) Error parsing JSON: Invalid value. while parsing string <html>
<head><title>414 Request-URI Too Large</title></head>
<body>
<center><h1>414 Request-URI Too Large</h1></center>
</body>
</html>
.,Source=Microsoft.DataTransfer.ClientLibrary.Odbc.OdbcConnector,''Type=System.Data.Odbc.OdbcException,Message=ERROR [HY000] [Microsoft][Hubspot] (100) Error parsing JSON: Invalid value. while parsing string <html>
<head><title>414 Request-URI Too Large</title></head>
<body>
<center><h1>414 Request-URI Too Large</h1></center>
</body>
</html>
.,Source=HubspotODBC_sb64.dll,'
"

The linked service connection to the API works, but fetching records from Contact_properties_values endpoint for us seems to make the copy activity crash with the error above.

As it is a linked service, the connector. I can't change the request from GET to POST if that would solve it, any ideas on how to proceed with debugging and solving this?
It had worked for months before this started happening.

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
9,603 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Evan Chatter 11 Reputation points
    2020-11-25T06:28:27.683+00:00

    Under Apache, the limit is a configurable value, LimitRequestLine. Change this value to something larger than its default of 8190 if you want to support a longer request URI. Extremely long URLs are usually a mistake. If you keep URLs under 2000 characters , they'll work in virtually any combination of client and server software. URI actually have a character limit depending on several things. Chrome limits url length of 2MB for practical reasons and to avoid causing denial-of-service problems in inter-process communication. On most platforms, Chrome's omnibox limits URL display to 32kB ( kMaxURLDisplayChars ) although a 1kB limit is used on VR platforms. IE - 2083 characters, Firefox - 2047 characters, Safari 80000 characters and Opera 190,000 characters.

    To resolve the problem :

    • By POST request: Convert query string to json object and sent to API request with POST
    • By GET request: Max length of request is depend on sever side as well as client side. Most webserver have limit 8k which is configurable. On the client side the different browser has different limit. The browser IE and Safari limit to 2k, Opera 4k and Firefox 8k. means the max length for the GET request is 8k and min request length is 2k.

    If exceed the request max length then the request truncated outside the limit by web server or browser without any warning. Some server truncated request data but the some server reject it because of data lose and they will return with response code 414.

    0 comments