This content has been marked as final. Show 2 replies
It's not a bug, it's just not behave as what you expected.
The count only strip out extra data AFTER proxy obtained the query result.
If you want to use limit filter, you will need to use ?q= syntax to add limit filter as part of your query.
Check section 28.5 of the Coherence client guide.
Not sure if CoHQL support LimitFilter, though.
Thanks for the reply.
I have read that paragraph of the documentation, all that is mentioned is that the results can be limited. It doesn't mention at which point in the query cycle the results are limited. Now from experiments both you and I know that the results are limited at the proxy. Coherence has a far superior way of limiting results, via a limit filter. I would argue that by not employing this mechanism when 'start and count' is encountered, could be viewed as a bug. At very least it's a significant optimization that could be made.
Presently it's all too easy to crash proxies with ill-formed queries. I just wanted to highlight this, and know if there was a workaround?