BatchGet Query Parameters in Request Body (Using Generated Clients)

[jjoyce0510]

Hi there!

We are running into an issue where the BatchGet that we are issuing via Rest.li generated client classes BatchGetEntityRequestBuilderBase creates a URL that is too long. The Rest.li server rejects the request with 414 status code.

Is there a way to instruct the client to send the batch of ids in a POST body instead of a GET query string, as detailed here?
https://linkedin.github.io/rest.li/Send-Rest_li-Request-Query-In-Request-Body#request-without-body

If not, will this be implemented in the auto-generated clients?

Thanks,
John

[jjoyce0510]

Any ideas here? You can see the associated issue in DataHub project above^

[karthikbalasub]

@jjoyce0510 The recommended way to get query tunneling working is by using the r2 client. It is preconfigured to run the ClientQueryTunnelFilter, which would automatically do the conversion to send the long URI in request body.

If you cannot use the R2 client, then I suggest using the QueryTunnelUtil::encode api to convert the request generated.

I don't think we can update the generated client builders to do this conversion as it would conflict with the implementation in the R2 filter. Also, any encoding done on client side would require a parallel decoding on server side (r2 ensures this by adding the query tunnel filter both on client and server side), which would be missing in this case.