Major Description
I noticed that if you attempt to bootstrap against a bucket that does not exist, then a NullReferenceException is thrown because parsing of the partial config returned fails.
|
|
{"rev":39,"nodesExt":[{"services":
{"capi":8092,"capiSSL":18092,"indexAdmin":9100,"indexHttp":9102,"indexHttps":19102,"indexScan":9101,"indexStreamCatchup":9104,"indexStreamInit":9103,"indexStreamMaint":9105,"kv":11210,"kvSSL":11207,"mgmt":8091,"mgmtSSL":18091,"n1ql":8093,"n1qlSSL":18093,"projector":9999},"thisNode":true}],"clusterCapabilitiesVer":[1,0],"clusterCapabilities":
{"n1ql":["enhancedPreparedStatements"]},"revEpoch":1}
|
|
The null reference exception happens when the BucketCapabilities is checked, but is null. This is confusing and a better exception should be thrown.