Support for optional query parameters for body-based requests
Description
As documented, the connector currently create a lookup query from the HTTP TableLookup Source to build either:
a query parameter list in case of a HTTP GET request
a body payload in case of a HTTP body-based request
There is no way to change this behaviour with custom factories.
Modification:
Change the signature of createLookupQuery(RowData lookupDataRow) in interface LookupQueryCreator so that it returns a class LookupQueryInfo holding:
the lookup query
the optional body-based query parameters
Adapt the creation of the URIs in the constructions of HTTP requests to retrieve information from the class LookupQueryInfo.
With these changes, any custom implementation of this interface that aims to provide body-based request is able to provide the lookup query as the payload and an optional formatted string representing the query parameters.
Support for optional query parameters for body-based requests
Description
As documented, the connector currently create a lookup query from the HTTP TableLookup Source to build either:
There is no way to change this behaviour with custom factories.
Modification:
Change the signature of createLookupQuery(RowData lookupDataRow) in interface
LookupQueryCreatorso that it returns a classLookupQueryInfoholding:Adapt the creation of the URIs in the constructions of HTTP requests to retrieve information from the class
LookupQueryInfo.With these changes, any custom implementation of this interface that aims to provide body-based request is able to provide the lookup query as the payload and an optional formatted string representing the query parameters.
Resolves #78
PR Checklist