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
Correctly set X-Partial-Results #879
Comments
plainolneesh
added a commit
to plainolneesh/datawave
that referenced
this issue
May 11, 2021
…than the requested page size
plainolneesh
added a commit
to plainolneesh/datawave
that referenced
this issue
May 13, 2021
…than the requested page size, corrected spelling
Just took a look at the related PR. Is there any more information on when X-Partial-Results isn't getting correctly set on the response? It seems that the logic is in place in RunningQuery, AbstractQueryLogicTransformer, and ResponseInterceptor. |
plainolneesh
added a commit
to plainolneesh/datawave
that referenced
this issue
Jun 2, 2021
…s than requested page size, update status
plainolneesh
added a commit
to plainolneesh/datawave
that referenced
this issue
Jun 2, 2021
…s than requested page size, update status
plainolneesh
added a commit
to plainolneesh/datawave
that referenced
this issue
Jun 2, 2021
…s than requested page size, update status
ivakegg
pushed a commit
that referenced
this issue
Nov 9, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
X-Partial-Results and PartialResults in the response should indicate whether we are returning less than the requested page size in a response.
The text was updated successfully, but these errors were encountered: