Hey @BenjaminPerryRoss , thanks for answering my concerns. I'd still argue that it's quite important to totally halt the startup if we can't instantiate the class the customer has configured and expects to use. If we just log a warning message and continue as it nothing bad had happened, it'll be much harder for them later in time to discover what went wrong after a query failure due to an non authorised method... it could get even worse if they "lose" the initial section of the log due to rolling (I've seen it happening). Maybe @nabarunnag or @jhuynh1 have some thoughts on this?.
[ Full content available at: https://github.com/apache/geode/pull/4161 ] This message was relayed via gitbox.apache.org for [email protected]
