Skip to content

9.0 - GetAliasResponse is initialized with Aliases set to null instead of empty #8502

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
Ramstad opened this issue Apr 24, 2025 · 0 comments · Fixed by #8505
Closed

9.0 - GetAliasResponse is initialized with Aliases set to null instead of empty #8502

Ramstad opened this issue Apr 24, 2025 · 0 comments · Fixed by #8505
Labels
9.x Relates to a 9.x client version Area: Client Category: Bug

Comments

@Ramstad
Copy link

Ramstad commented Apr 24, 2025

Elastic.Clients.Elasticsearch version: 9.0.0

Elasticsearch version: 9.0.0

.NET runtime version: net9.0

Operating system version: Windows for client, docker for elasticsearch

Description of the problem including expected versus actual behavior:
GetAliasResponse is now initialized with Aliases being null instead of empty dictionary. This causes IsValidResponse and the depending DebugInformation to fail with System.NullReferenceException when no matching alias exists.
Expected result is for IsValidResponse not to throw, either by dictionary being empty, or by checking for nulls.

@flobernd flobernd added Category: Bug Area: Client 9.x Relates to a 9.x client version labels Apr 28, 2025
@flobernd flobernd mentioned this issue Apr 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
9.x Relates to a 9.x client version Area: Client Category: Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants