When calling WinRMWqlExecutor (WinRMWqlExecutor.java) there is no way to set the maxElements which will eventually be used in the pull (WinRMService.java#L490). Without being able to set this, it defaults to 1 max element, in which case a new request is used for every element. This leads to extremely long WQL poll times.
I suggest adding an optional parameter to pull and allowing users to pass it in when making WQL queries. This will greatly improve poll times for WQL queries that return large responses. The Pull class already supports maxElements so it should just be a matter of feeding the parameter from the top level call and setting it on the pull method similar to setEnumerationContext here
When calling WinRMWqlExecutor (WinRMWqlExecutor.java) there is no way to set the maxElements which will eventually be used in the pull (WinRMService.java#L490). Without being able to set this, it defaults to 1 max element, in which case a new request is used for every element. This leads to extremely long WQL poll times.
I suggest adding an optional parameter to pull and allowing users to pass it in when making WQL queries. This will greatly improve poll times for WQL queries that return large responses. The Pull class already supports maxElements so it should just be a matter of feeding the parameter from the top level call and setting it on the pull method similar to setEnumerationContext here