-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Implement auto-upgrade mechanism for joda-java migration #45548
Comments
Pinging @elastic/es-core-infra |
I wonder to what degree this should be automatic. It might be easy to implement a simple regexp where |
Similar logic that allows reindex exists at the moment in kibana but there is plan to migrate some of this to ES plugin. |
I don't think we can do this automatically since we can't distinguish when they actually wanted |
I thought this change would go to 6.8 where the context of pattern without of an 8 prefix should be clear |
I think it is safe to assume that if the format In other words, if it was wrong previously, it will be wrong after the change as well, but in a consistent manner. Cheers, Richie |
@pgomulka Is this work still planned? Since we are now developing 7.x and 8.x, I am not sure if an upgrade mechanism for 6.8.x will be useful. |
Given that we haven't had anymore requests for this in many years, and we are fully using Java time formats, I'm going to close this issue. |
it requires at the moment a new mapping creation and a reindex in order to fix date formats. This is a bit tedious for users, especially when their formats were compatible like
YYYY-MM-dd
=>yyyy-mm-dd
We should implement a mechanism that will automatically upgrade the mapping for users in situations like this. If it won't be able to confirm 100% that the mapping can be autoupgraded, it should not do any action and user would be forced to create new mapping/reindex (as he has to now)
We could consider to allow mapping modifications for these fields. Or use a reindex with alias to allow smooth migration (and still allowing to index documents)
The text was updated successfully, but these errors were encountered: