Default limit value is not applied on searches #1775
Closed
Comments
kroepke
added a commit
that referenced
this issue
Feb 10, 2016
the builder didn't properly default a 0 value to the actual default fixes issue #1775
kroepke
added a commit
that referenced
this issue
Feb 10, 2016
- add test for negative limit - actually test the explicit limit as well (so it doesn't get overridden by the default handling) fixes issue #1775
ah duh :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using the current master, the default limit parameter for searches is not working. Here's the result of the query
http://hostname:12900/search/universal/relative?query=*&range=3600&pretty=true
:As you can see, the search is returning 10 results instead of 150. Looking a bit through the code, I saw that the limit applied in
SearchesConfig.Builder
is overrode by setting a 0limit
afterwards, and that is happening in some places where we rely on the default limit.The text was updated successfully, but these errors were encountered: