PubsubInboundChannelAdapter swallows error when connected to non-existent subscription about spring-cloud-gcp HOT 5 CLOSED

The .awaitRunning() is not good. It eliminates the purpose of the startAsync().

Would be better to use void addListener(ApiService.Listener var1, Executor var2); to log in case of
failed(ApiService.State from, Throwable failure)

from spring-cloud-gcp.

Another (more expensive, but more explicit) alternative is to make an explicit check for the existence of the Subscription using the getSubscription() method. We could also create the Subscription if it doesn't exist.

This behaviour should be parameterised.

from spring-cloud-gcp.

@artembilan logging sounds good, however, that still doesn't solve the need from the client code to have an explicit way to inspect/handle subscription errors and have the option to fail/retry/ignore.
@joaoandremartins I like the idea of having the option to auto-create the subscription.

I guess we could combine the two suggested behaviors: we listen on the lifecycle events and "on failure" we can inspect if the error is due to missing subscription ("NOT_FOUND: Resource not found (resource=[subscription])." and if that's the case we can have a configurable behavior + a status accessible from the client side probably via a status listener?

from spring-cloud-gcp.

Well, in other places we expose the ApplicationEvent architecture to let end-user to do what is the best for him there. For example ListenerContainerConsumerFailedEvent in the Spring AMQP: http://docs.spring.io/spring-amqp/reference/html/_reference.html#consumer-events. Or MqttIntegrationEvent hierarchy: http://docs.spring.io/spring-integration/reference/html/mqtt.html#mqtt-inbound

from spring-cloud-gcp.

This was apparently fixed in a recent version of the google-cloud-pubsub library, as I'm now seeing errors logged when trying to subscribe to a non-existing subscription.

from spring-cloud-gcp.