Upsert/Get KV operation hangs indefinitely when the target collection does not exists.

[AradhyaK22]

We came across this issue where the operation simply hangs with no error propagating back to the caller, and also couldn't find a way to set a timeout on KV operations.

  self.default_scope()
            .collection("test_collection") //test_collection doesn't exists
            .upsert(key, value, None)
            .await
            .map_err(map_error)?;

[chvck]

Hi @AradhyaK22 it is expected that performing operations against collections that don't exist won't return errors. It's a design philosophy behind the current version of the Couchbase SDKs - it's expected that if a collection doesn't exist then the SDK will keep retrying behind the scenes as the collection is expected to come online eventually. If you enable logging you should see that the SDK is sending get-collectiion-id requests.

We have currently chosen to not implement operation timeouts in the rust SDK as applications just dropping the operation future seems more idiomatic to the rust ecosystem. To that end we'd expect an application that needs to specify a timeout (e.g. there isn't a http server controlling how long an operation can take) to use select! or something like https://docs.rs/tokio/latest/tokio/time/fn.timeout.html. We're interested in feedback on our stance on this.