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
Bug: QueryExecutorBean can throw INVALID_MAX_RESULTS_OVERRIDE error when it shouldn't #2251
Labels
bug
Something isn't working
Comments
keith-ratcliffe
added a commit
that referenced
this issue
Jan 31, 2024
keith-ratcliffe
added a commit
that referenced
this issue
Jan 31, 2024
keith-ratcliffe
added a commit
that referenced
this issue
Jan 31, 2024
keith-ratcliffe
added a commit
that referenced
this issue
Jan 31, 2024
keith-ratcliffe
added a commit
that referenced
this issue
Feb 5, 2024
hgklohr
added a commit
that referenced
this issue
Feb 23, 2024
hgklohr
added a commit
that referenced
this issue
Feb 23, 2024
hgklohr
added a commit
that referenced
this issue
Feb 23, 2024
hgklohr
added a commit
that referenced
this issue
Feb 23, 2024
hgklohr
added a commit
that referenced
this issue
Feb 23, 2024
drewfarris
pushed a commit
that referenced
this issue
Feb 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug 1
If the user specifies a
max.results.override
that exceeds max results for the given QueryLogic,DatawaveErrorCode.INVALID_MAX_RESULTS_OVERRIDE
will be thrown in validateQuery even though the override should be permissible based on other configured overrides, such as those defined for specificDN
and/orsystemFrom
valuesBug 2
There is an additional bug on the line above that would cause
DatawaveErrorCode.INVALID_MAX_RESULTS_OVERRIDE
to be thrown for users with theUNLIMITED_QUERY_RESULTS_USER
role, if they do not also possess thePRIVILEGED_USER
roleThe text was updated successfully, but these errors were encountered: