This commit fixes invalid documentation references to
`spring.pulsar.consumer.subscription.type` configuration property.
This commit is contained in:
Vedran Pavic
2024-08-29 20:55:36 +02:00
committed by GitHub
parent 9064623fb1
commit 01a95a70a2
2 changed files with 2 additions and 2 deletions

View File

@@ -15,7 +15,7 @@ Spring Boot provides this consumer factory which you can further configure by sp
TIP: The `spring.pulsar.consumer.subscription.name` property is ignored and is instead generated when not specified on the annotation.
TIP: The `spring.pulsar.consumer.subscription-type` property is ignored and is instead taken from the value on the annotation. However, you can set the `subscriptionType = {}` on the annotation to instead use the property value as the default.
TIP: The `spring.pulsar.consumer.subscription.type` property is ignored and is instead taken from the value on the annotation. However, you can set the `subscriptionType = {}` on the annotation to instead use the property value as the default.
Let us revisit the `PulsarListener` code snippet we saw in the quick-tour section:

View File

@@ -122,7 +122,7 @@ Spring Boot provides this consumer factory which you can further configure by sp
TIP: The `spring.pulsar.consumer.subscription.name` property is ignored and is instead generated when not specified on the annotation.
TIP: The `spring.pulsar.consumer.subscription-type` property is ignored and is instead taken from the value on the annotation. However, you can set the `subscriptionType = {}` on the annotation to instead use the property value as the default.
TIP: The `spring.pulsar.consumer.subscription.type` property is ignored and is instead taken from the value on the annotation. However, you can set the `subscriptionType = {}` on the annotation to instead use the property value as the default.
=== Generic records with AUTO_CONSUME
If there is no chance to know the type of schema of a Pulsar topic in advance, you can use the `AUTO_CONSUME` schema type to consume generic records.