You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As a user of the date processor, I am unable to format the result of the conversion of my dates to ISO_8601 format strings. The result of the string is always the entire timestamp String (2023-07-23T15:28:15.081-05:00).
Describe the solution you'd like
An optional parameter in the date processor named destination_format. This format can be https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html similar to the OpenSearch index, and will take the ISO_8601 timestamp String that is generated by the Date processor and format it to the DateTimeFormat specified
Describe alternatives you've considered (Optional)
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
As a user of the date processor, I am unable to format the result of the conversion of my dates to ISO_8601 format strings. The result of the string is always the entire timestamp String (
2023-07-23T15:28:15.081-05:00
).Describe the solution you'd like
An optional parameter in the
date
processor nameddestination_format
. This format can be https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html similar to the OpenSearch index, and will take the ISO_8601 timestamp String that is generated by the Date processor and format it to the DateTimeFormat specifiedDescribe alternatives you've considered (Optional)
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: