We have our documents indexed in Elastic search. Each of these documents has date field captured without the timezone (By default, we are capturing the date in IST timezone, without the timezone). For obvious reasons, this is not right.
We are planning to capture date in UTC timezone and migrate all existing documents to capture the date in UTC timezone. After going through a couple of documents, I did not get any definitive guide to do this.
Need some expert opinion on how to solve this issue. Really appreciate every opinion.
Script Processor : Used to add default timezone for the Date fields.
Date Processor : Used for converting the timezone and copy the value to new field
Rename and Remove Processors : For getting back the original document structure without the intermediate fields which got created during processing.
But facing one challenge. We have the date field captured at the document root level and at the nested level as well. How can we use the script processor for setting the default timezone value at the nested activities level? Really appreciate your quick suggestion on this.
@Nakshathri could you help me here and instead of describing the issue piece by piece post the simulate pipeline command with your test data and pipeline that reproduces the issue, so I can run it locally to see what's going on?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.