Skip to content

Defining a custom ElasticsearchTransport causes the auto-configured JsonpMapper to back off #36698

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.

Sign up for GitHub

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

Jump to bottom
Closed
wilkinsona opened this issue Aug 3, 2023 · 0 comments
Closed

Defining a custom ElasticsearchTransport causes the auto-configured JsonpMapper to back off #36698

wilkinsona opened this issue Aug 3, 2023 · 0 comments
Assignees
@wilkinsona
Labels
type: bug A general bug
Milestone
3.0.10

Comments

@wilkinsona
Copy link
Member

As discussed in #36669, defining a custom ElasticsearchTransport bean causes the auto-configuration of a JsonpMapper to back off. This is inconvenient as you may want to use the JsonpMapper in your custom transport.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wilkinsona wilkinsona

Labels
type: bug A general bug
Projects
None yet
Milestone
3.0.10
Development

No branches or pull requests
1 participant
@wilkinsona