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.
Currently, date processor parses the timestamp and stores in destination field which is of String type.
Describe the solution you'd like
In scenario's, when the integer value of destination field is needed, we could use this convert_entry_type processor to convert the destination field to long, because using integer is not feasible for epoch times.
The text was updated successfully, but these errors were encountered:
@Utkarsh-Aga , I agree with you. Being able to convert to a long makes sense and is needed at certain times. We'd be happy to review and accept a PR. I'll assign this to you.
Is your feature request related to a problem? Please describe.
Currently,
date
processor parses the timestamp and stores indestination
field which is ofString
type.Describe the solution you'd like
In scenario's, when the integer value of
destination
field is needed, we could use thisconvert_entry_type
processor to convert thedestination
field tolong
, because usinginteger
is not feasible forepoch
times.The text was updated successfully, but these errors were encountered: