You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While most extension functionality is receiving requests and sending responses, some functionality sends requests the other way. The request/response pairs are matched by their request_id fields, which requires handling them in a particular order. The below sequence would have to be repeated for any other outbound requests.
Pass the id as a key to the response handler registry, and a handler as a value
Finally send the request from step 1
What solution would you like?
A single class where I can pass the request from step 1 and the handler from step 3 as arguments, and it handles extracting the key and actually sending the request.
What alternatives have you considered?
Add the functionality to the Request Handler abstract class, or add it to another abstract parent class.
Is your feature request related to a problem?
While most extension functionality is receiving requests and sending responses, some functionality sends requests the other way. The request/response pairs are matched by their request_id fields, which requires handling them in a particular order. The below sequence would have to be repeated for any other outbound requests.
opensearch-sdk-py/src/opensearch_sdk_py/actions/internal/discovery_extensions_request_handler.py
Lines 52 to 66 in 7dc19ea
We have to:
What solution would you like?
A single class where I can pass the request from step 1 and the handler from step 3 as arguments, and it handles extracting the key and actually sending the request.
What alternatives have you considered?
Add the functionality to the Request Handler abstract class, or add it to another abstract parent class.
Do you have any additional context?
https://www.explainxkcd.com/wiki/index.php/353:_Python
The text was updated successfully, but these errors were encountered: