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

fix #4029: Use enum item.Name instead of Enum.GetName to get enum value #4032

Merged
merged 1 commit into from
Aug 20, 2019
Merged

fix #4029: Use enum item.Name instead of Enum.GetName to get enum value #4032

merged 1 commit into from
Aug 20, 2019

Conversation

sklirg
Copy link
Contributor

@sklirg sklirg commented Aug 19, 2019

This is the propsed fix from the original repo of the code: neuecc/Utf8Json#129

Resolves #4029

I've tested this locally in a .NET Framework project and it works, compared to previously where it'd throw with an exception as mentioned in #4029.

I'm not sure if this should target 7.x or the master branch.

This is the propsed fix from the original repo of the code: neuecc/Utf8Json#129
@russcam
Copy link
Contributor

russcam commented Aug 19, 2019

Thanks for opening this, @sklirg 👍 Targeting master is best, we can backport to 7.x then.

@russcam russcam merged commit 0c84c59 into elastic:master Aug 20, 2019
@russcam
Copy link
Contributor

russcam commented Aug 20, 2019

ported to 7.x: 7d974ac

@sklirg sklirg deleted the fix/4029-enum-get-type-throwing branch August 20, 2019 07:17
@sklirg
Copy link
Contributor Author

sklirg commented Aug 21, 2019

Is there a planned release that includes this fix in the near future? :-) Would love to have this in our testing environment to make sure our upgrade to 7.x works smoothly in production as well.

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.

"Key was already exists" on NEST indexing after upgrading from ES v6.8.1
2 participants