Skip to content

DefaultKafkaHeaderMapper - Use Pattern Matchers for Inbound Mapping #2321

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

Closed
garyrussell opened this issue Jun 28, 2022 · 0 comments · Fixed by #2322
Closed

DefaultKafkaHeaderMapper - Use Pattern Matchers for Inbound Mapping #2321

garyrussell opened this issue Jun 28, 2022 · 0 comments · Fixed by #2322

Comments

@garyrussell
Copy link
Contributor

Add the ability to suppress mapping headers for inbound mapping.

Currently, the matchers are only used for outbound mapping; however, the default never match matchers need to be skipped for inbound mapping.

@garyrussell garyrussell added this to the 3.0.0.M5 milestone Jun 28, 2022
garyrussell added a commit to garyrussell/spring-kafka that referenced this issue Jun 28, 2022
garyrussell added a commit to garyrussell/spring-kafka that referenced this issue Jun 28, 2022
garyrussell added a commit to garyrussell/spring-kafka that referenced this issue Jun 28, 2022
artembilan pushed a commit that referenced this issue Jun 28, 2022
Resolves #2321

**cherry-pick to 2.9.x, 2.8.x**
artembilan pushed a commit that referenced this issue Jun 28, 2022
Resolves #2321

**cherry-pick to 2.9.x, 2.8.x**
artembilan pushed a commit that referenced this issue Jun 28, 2022
Resolves #2321

**cherry-pick to 2.9.x, 2.8.x**

# Conflicts:
#	spring-kafka/src/main/java/org/springframework/kafka/support/AbstractKafkaHeaderMapper.java
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant