-
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
Support Elasticsearch date-mapping pattern names in DateProcessor #23032
Comments
Pinging @elastic/es-core-infra |
This is related to #27330 - I will look up, if the date formats can be easily converted to java time. If that's the case, it makes sense to add this to the data processor, otherwise we would add something that might be deprecated soon. |
@spinscale cool. another thing to note about why this wasn't tackled yet is that we want to keep Ingest independent of ES as much as possible (via #29233) |
@talevy We discussed this in FixItThursday, and think we should just fix this (in conjunction with the java 8 time api work), as the separation of ingest from ES has a lot of other blockers, and should not prohibit fixing this issue. |
This has been open for quite a while, and hasn't had a lot of interest. For now I'm going to close this as something we aren't planning on implementing. We can re-open it later if needed. |
as mentioned here: #22982, it would be nice to use ES's built-in formats listed out here: https://www.elastic.co/guide/en/elasticsearch/reference/5.x/mapping-date-format.html#built-in-date-formats.
Like
The text was updated successfully, but these errors were encountered: