CQ tests were failing because the `getQueryService()` method on client side (invoked when creating the new `ExecutionContext`) causes an implicit `DEFAULT` Pool [initialization](https://github.com/apache/geode/blob/develop/geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java#L4186-L4196), which can not be avoided when using custom pools as the tests do. The `ExecutionContext` now uses a no-op authorizer when created from a client cache: authorization and authentication logic happens only on server side anyways, and the authorizer will be obtained from the cluster configuration service directly instead of the query service when OQL security is fully implemented ([GEODE-6983](https://issues.apache.org/jira/browse/GEODE-6983)).
[ Full content available at: https://github.com/apache/geode/pull/4169 ] This message was relayed via gitbox.apache.org for [email protected]
