Arbitrary query parameters set via RequestBuilder.queryParam(...) are ignored when used in conjunction with a search via POST.
Adding something like
service.searchRequest("Users").
filter(filter).
queryParam(expectedKey, expectedValue).
invokePost(UserResource.class);
to EndpointTestCase.testQueryParams() should reproduce this.
Note that there isn't actually an implementation yet. For the client to set these parameters, logic needs to be added to SearchRequestBuilder.invoke(boolean, SearchResultHandler<T>, Class<T>), similar to the existing logic there for handling arbitrary headers. Then, support will need to be added to the server component, in DotSearchFilter, I assume.