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
The error I'm expecting is "Sort operation used more than the maximum 33554432 bytes of RAM" which can be seen when streaming is not used. When streaming, the response is "successful" but has no results. To me this tells me mongo is throwing the same error (to mongo it is the same request) but lightblue is handling it differently when streaming is used.
The text was updated successfully, but these errors were encountered:
Exception is thrown when the first result is retrieved from the cursor. This happens in the REST layer, and there, exceptions are ignored.
I think the best way to handle this is to change the cursor code so that we retrieve the first result when cursor is constructed, and deal with the errors then and there.
The error I'm expecting is "Sort operation used more than the maximum 33554432 bytes of RAM" which can be seen when streaming is not used. When streaming, the response is "successful" but has no results. To me this tells me mongo is throwing the same error (to mongo it is the same request) but lightblue is handling it differently when streaming is used.
The text was updated successfully, but these errors were encountered: