-
Notifications
You must be signed in to change notification settings - Fork 417
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
User.hash vs. new hash.* fields #483
Comments
I agree with this. Would a PR for this be accepted? |
It's a good point, thanks for offering to submit a PR. Since this would be a breaking change, I suggest we keep that discussion open and consider it for ECS 2.0 / Elastic Stack 8.0. |
Since this issue was opened, the I can see value to having the various Having a single field remain that holds the "anonymised" value of the |
#426 added hash.* fields but "user" already contains hash. So user.hash should become user.hash.*.
The text was updated successfully, but these errors were encountered: