-
Notifications
You must be signed in to change notification settings - Fork 418
Open
Description
What would you like to happen?
Will be great to have a native support to use custom HTTP Methods over the REST Client transform.
When using the existing option Method field name passing LIST as Method, an exception is raised.
org.apache.hop.core.exception.HopException:
Can not read result from [ENDPONT]
Request could not be processed
Method [LIST] is unknown! The supported methods are :
GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
To workaround this today you need to handle those API calls outside of Apache Hop using the Execute a Process transform, which is not ideal and brings some others issues when developing and deploy to different OS (Windows to Linux).
I don't know what are the actual limitations and why it can't handle the request, but if we can pass the Method as field, I thought it would be possible to receive any method your endpoint expect you to use, not just the dafault set.
Issue Priority
Priority: 3
Issue Component
Component: Transforms
steewel