simonz-bq commented on PR #1697: URL: https://github.com/apache/tinkerpop/pull/1697#issuecomment-1160709486
> if so, what circumstance allows that to happen and how does this change either potentially fix or better expose that problem? In the case that initializing the connection pool had a failure *but* somehow the cluster has available hosts `cluster.availableHosts().isEmpty()` in the list (not necssarily alive), there wouldn't be a connection pool initialized but an error would not be throw because of this check being possibly false. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@tinkerpop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org