Skip to content

Add default variant for Normalizer #706

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
wants to merge 1 commit into from

Conversation

KovalDS
Copy link

@KovalDS KovalDS commented Nov 14, 2023

Apply similar logic as in #522, but for Normalizers:
If type is not specified, then this is a CustomNormalizer

Fixes #696

Copy link

cla-checker-service bot commented Nov 14, 2023

💚 CLA has been signed

@KovalDS KovalDS force-pushed the fix-default-normalizer branch from 07b6a84 to 734b92b Compare November 15, 2023 10:12
@KovalDS
Copy link
Author

KovalDS commented Nov 15, 2023

@swallez, Would you mind reviewing this PR, please? This is exact same issue that you've fixed for analyzer.

Also, to backport to 7.17 should I open PR manually to 7.17 branch?

@l-trotta
Copy link
Contributor

Hello! Unfortunately we cannot accept PRs that modify the co.elastic.clients.elasticsearch package, since it's autogenerated and everything would be overwritten at the following generation. The mentioned issue was recently fixed in the api spec used to generate the java client and will be part of the next release.

@l-trotta l-trotta closed this May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error deserializing co.elastic.clients.elasticsearch._types.analysis.Normalizer: Property 'type' not found
2 participants