Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apply spring.pulsar.consumer.subscription.name to auto-configured Pulsar listener container #42067

Closed

Conversation

onobc
Copy link
Contributor

@onobc onobc commented Aug 30, 2024

The subscription name config prop was not being set on the Pulsar listener container properties. This commit adds the subscription name to the Pulsar property mappers.

Resolves #42053

The subscription name config prop was not being set on the Pulsar
listener container properties. This commit adds the subscription
name to the Pulsar property mappers.

Resolves spring-projects#42053
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Aug 30, 2024
@philwebb philwebb added type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged labels Sep 1, 2024
@philwebb philwebb added this to the 3.4.x milestone Sep 1, 2024
@wilkinsona
Copy link
Member

Should we be treating this as a bug, @onobc? The property and the API to apply it seem to be there in Boot 3.2. Should we apply the change to 3.2.x and later or only to main?

@wilkinsona wilkinsona added the status: waiting-for-internal-feedback An issue that needs input from a member or another Spring Team label Sep 4, 2024
@vpavic
Copy link
Contributor

vpavic commented Sep 4, 2024

My understanding is that this depends on changes Chris did in spring-projects/spring-pulsar#821 meaning this is a 3.4 target.

@onobc
Copy link
Contributor Author

onobc commented Sep 4, 2024

@vpavic summary is correct. The property is there and still does configure the default consumer factory but the property is ignored when it comes to the message container (i.e. @PulsarListener). The Spring Pulsar docs point this limitation out so I consider this an improvement so the property is respected in all applicable areas.

@wilkinsona
Copy link
Member

Thanks, both.

@wilkinsona wilkinsona removed the status: waiting-for-internal-feedback An issue that needs input from a member or another Spring Team label Sep 4, 2024
@wilkinsona wilkinsona self-assigned this Sep 5, 2024
@wilkinsona wilkinsona changed the title Add subscription name to Pulsar mapped config props Apply spring.pulsar.consumer.subscription.name to auto-configured Pulsar listener container Sep 5, 2024
@wilkinsona wilkinsona modified the milestones: 3.4.x, 3.4.0-M3 Sep 5, 2024
wilkinsona pushed a commit that referenced this pull request Sep 5, 2024
The subscription name config prop was not being set on the Pulsar
listener container properties. This commit adds the subscription
name to the Pulsar property mappers.

See gh-42067
@wilkinsona wilkinsona closed this in 0bc2761 Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement A general enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarify purpose of Pulsar consumer subscription related properties
5 participants