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
found unknown setting WARN messages #20946
Comments
Yes, warn is the right level! We are ignoring settings a user thinks they have set, we absolutely should warn them. |
Sounds good, can we add the index name reference though ? :) So end users will not have to query the index settings api to figure out where these settings are originally set. |
Yes, of course. I was only commenting on the warn request. If I disagreed with both requests I would have closed the issue. 😇 |
Cool, thx again! |
I have a fix for this. I'll open a PR soon. |
And thanks for this too! @jasontedor |
5.0.0-rc1
Filing from a logging cleanup pt of view.
I get what we are saying here for this is being logged on 5.x against older Marvel indices.
But does this have to be logged at the WARN level? Seems like a normal migration routine that it goes through? Does the end user need to know this? If so, can we include the index name that it changed and maybe move these to the INFO level, etc.. :)
The text was updated successfully, but these errors were encountered: