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

Add long as a target type for convert_entry_type processor #4120

Closed
Utkarsh-Aga opened this issue Feb 13, 2024 · 3 comments · Fixed by #4359
Closed

Add long as a target type for convert_entry_type processor #4120

Utkarsh-Aga opened this issue Feb 13, 2024 · 3 comments · Fixed by #4359
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@Utkarsh-Aga
Copy link
Contributor

Utkarsh-Aga commented Feb 13, 2024

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.

@Utkarsh-Aga
Copy link
Contributor Author

If the team is okay to have this feature, then I would be more than happy take a shot at it and raise a PR.

@asifsmohammed asifsmohammed added enhancement New feature or request and removed untriaged labels Feb 13, 2024
@dlvenable
Copy link
Member

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

@Utkarsh-Aga
Copy link
Contributor Author

Sure, Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

3 participants