-
Notifications
You must be signed in to change notification settings - Fork 84
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
Make the APIDataset.save stores the response received #748
Comments
This is a great point, I think the other slightly more robust way to do this would is to add a |
Ah right I didn't think to this way. In our case, some of the external endpoints send back to us an id and some pieces of information that we use as starting point of another pipeline in a subsequent run so the idea of storing the response. |
That makes sense, I think the ambition is right, we should store this. I guess this was built under the assumption we only cared about |
Great, I will make a PR then. |
It makes total sense to me to save the response. I wouldn't save it as an other type of dataset though (e.g. |
@merelcht I see, regarding the use of When you say
do you mean use directly the |
Description
When running a
POST
orPUT
request with theAPIDataset
, the response is currently lost while it would be useful to store it.Context
We rely a lot on the APIDataset to fetch but also to save data to external API. Keeping tracks or the answer is then really important to us.
Possible Implementation
We built a custom
APIDataset
that takes afilepath
argument. If this argument is not None, aTextDataset(filepath=filepath)
is created and is called in the_execute_save_request
:Possible Alternatives
Not found any other.
I would then like to make a PR with this proposed change but before making the actual PR, I wanted to double check with you that this feature would be of interest for the community.
The text was updated successfully, but these errors were encountered: