Date time with time multifield

[stephenb (Stephen Brown)]

Hi @RRGTHWAR1 Welcome to the community...

@RRGTHWAR1

For example, created_date would be the full datetime, and created_date.time would store only the time portion,

No that is not supported / that is not how multifields work... See here

It is often useful to index the same field in different ways for different purposes. This is the purpose of multi-fields . For instance, a string field could be mapped as a text field for full-text search, and as a keyword field for sorting or aggregations:

you will need to use 2 separate fields like

created_date 
created_time_of_day

@RRGTHWAR1

Would there be some way to store the modulo of the milliseconds at indexing time to remove the days from them

Yes you would do this at index time using. an ingest pipeline with a script processor... but the result would be a long

I think I showed just how to do something similar recently as a runtime field a script processor would be very similar

Extracting time from @timestamp field using Runtime

Add the mapping to the template and a script process to the ingest pipeline... and you do not need the @ for every timestamp / date that is just and nameing convtion for the special field @timestamp take a look at this... POST _ingest/pipeline/_simulate { "pipeline": { "processors": [ { "script": { "lang": "painless", "source": """ZonedDateTime zdt = ZonedDateTime.parse(ctx['@timestamp'], DateTimeFormatter.ISO_ZONED_DATE_TIME); String time_of_…

This would actually create a "keyword" that shows the time of day it could be filtered...

If you just want ms, that would be a long, and of course, that would not be a date. It would just be a long...