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

Support Elasticsearch date-mapping pattern names in DateProcessor #23032

Closed
talevy opened this issue Feb 8, 2017 · 5 comments
Closed

Support Elasticsearch date-mapping pattern names in DateProcessor #23032

talevy opened this issue Feb 8, 2017 · 5 comments
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement Team:Data Management Meta label for data/management team

Comments

@talevy
Copy link
Contributor

talevy commented Feb 8, 2017

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

"date": {
  "field": ...,
  "target_field": ...,
  "formats": [ "basic_date_time_no_millis" ]
}
@talevy talevy added :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement labels Feb 8, 2017
@talevy talevy self-assigned this Feb 8, 2017
@talevy talevy added discuss >enhancement :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP and removed :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement labels Mar 15, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@spinscale
Copy link
Contributor

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.

@talevy
Copy link
Contributor Author

talevy commented Mar 28, 2018

@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)

@rjernst
Copy link
Member

rjernst commented Jul 5, 2018

@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.

@talevy talevy removed their assignment Jul 19, 2018
@rjernst rjernst added the Team:Data Management Meta label for data/management team label May 4, 2020
@dakrone
Copy link
Member

dakrone commented May 8, 2024

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.

@dakrone dakrone closed this as not planned Won't fix, can't repro, duplicate, stale May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement Team:Data Management Meta label for data/management team
Projects
None yet
Development

No branches or pull requests

6 participants