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
Importing can take a long time, and it's common to cause response timeouts on even middle-sized CSV files (dozens of rows).
A good solution is to use a StreamingHTTPResponse object instead of a regular HTTPResponse (like proposed for #3). In this way the server processes the import one instance at a time, sending to the client the import result (success or error) in real time, thus avoiding the timeout and as a side-effect enhancing user experience.
On the frontend side consider using something like OboeJS to parse the streaming JSON that the server will send with the successes or errors of each row.
The text was updated successfully, but these errors were encountered:
Importing can take a long time, and it's common to cause response timeouts on even middle-sized CSV files (dozens of rows).
A good solution is to use a StreamingHTTPResponse object instead of a regular
HTTPResponse
(like proposed for #3). In this way the server processes the import one instance at a time, sending to the client the import result (success or error) in real time, thus avoiding the timeout and as a side-effect enhancing user experience.On the frontend side consider using something like OboeJS to parse the streaming JSON that the server will send with the successes or errors of each row.
The text was updated successfully, but these errors were encountered: