-
Notifications
You must be signed in to change notification settings - Fork 362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request]: Rest Transform Timeout #3811
Comments
nadment
added a commit
to nadment/hop
that referenced
this issue
May 7, 2024
Fix Http transform connection timeout (confusion with socket timeout)
nadment
added a commit
to nadment/hop
that referenced
this issue
May 7, 2024
Fix Http transform connection timeout (confusion with socket timeout)
nadment
added a commit
to nadment/hop
that referenced
this issue
May 7, 2024
Fix Http transform connection timeout (confusion with socket timeout)
@nadment maybe we should add an indicator to the label. is that timeout in seconds? milliseconds? |
nadment
added a commit
to nadment/hop
that referenced
this issue
May 7, 2024
Fix Http transform connection timeout (confusion with socket timeout)
I've added the indication and updated the document too. |
hansva
added a commit
that referenced
this issue
May 8, 2024
Add connection timeout and read timeout to Rest transform #3811
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to happen?
Observed
Currently calling a rest transform that takes too much time will quicky abort the process due to a hardcoded timeout value.
the timeout is currently hardcooded in ApacheHop, Bart Maerens confirmed on Mon 26/02/2024 20:28 that this is not yet possible (thanks for the quick confirmation)
Expected
Allow to specify a timeout in the rest transform.
maybe as a quick and dirty (interim) solution : allow to set a global parameter for all rest transform (you will not need to change the UI)
Issue Priority
Priority: 2
Issue Component
Component: Hop Gui, Component: Hop Server, Component: Hop Web
The text was updated successfully, but these errors were encountered: