Hey,
I don't know if I am missing something but;
I tried to upgrade the dependency of spring-cloud-gcp-starter-pubsub in my project (spring-boot 2.1.4.RELEASE) to 1.2.2.RELEASE and then started it, I got some errors about PubSubHealthIndicator:
2020-03-06T11:43:16,046 INFO (1)main [AnnotationUtils.java:1973]: Failed to introspect annotations on class org.springframework.cloud.gcp.autoconfigure.pubsub.health.PubSubHealthIndicatorAutoConfigurationEnhancerBySpringCGLIB6ba30de8: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
2020-03-06T11:43:16,059 INFO (1)main [PostProcessorRegistrationDelegate.java:330]: Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfigurationEnhancerBySpringCGLIB6b3fbf4] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
I think it is because "HealthContributorAutoConfiguration" class used in "PubSubHealthIndicatorAutoConfiguration" is added to SpringBoot after 2.2.0, so it does not work with Spring Boot versions below that one!
Hello everyone!
I'm having some issues enabling Stackdriver Trace in a project that is using FirestoreReactiveRepository.
Having tracing enabled with spring-cloud-gcp-starter-trace and doing something basic like fetching a document with a specific id will result in:
'org.springframework.cloud.gcp.data.firestore.FirestoreDataException: Error while reading entries by id; nested exception is io.grpc.StatusRuntimeException: UNIMPLEMENTED: GRPC target method can't be resolved.'
Is this not currently supported?
spring-integration
in combination with spring-cloud-gcp
to handle messages in batches. For this purposes, AggregatingMessageHandler
expects me to provide a CorrelationStrategy
, of which I don't have any for Pub/Sub. Receiving messages in batches in random order is perfectly fine by me. How shall I pass a CorrelationStrategy
in this case?
CorrelationStrategy
against every incoming message.
ReleaseStrategy
is satisfied, the aggregator releases a whole group with messages arrived to it so far
pullAndAck()
otherwise:
/**
* Pull and auto-acknowledge a number of messages from a Google Cloud Pub/Sub subscription.
* @param subscription canonical subscription name, e.g., "subscriptionName", or the fully-qualified
* subscription name in the {@code projects/<project_name>/subscriptions/<subscription_name>} format
* @param maxMessages the maximum number of pulled messages. If this value is null then
* up to Integer.MAX_VALUE messages will be requested.
* @param returnImmediately returns immediately even if subscription doesn't contain enough
* messages to satisfy {@code maxMessages}
* @return the list of received messages
*/
List<PubsubMessage> pullAndAck(String subscription, Integer maxMessages, Boolean returnImmediately);
subscribe
is not batch'able
pull
you are on your own
PubSubMessageSource
subscribe
semantics