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

[FEATURE] Support grok command in PPL #814

Closed
joshuali925 opened this issue Sep 9, 2022 · 1 comment · Fixed by #813
Closed

[FEATURE] Support grok command in PPL #814

joshuali925 opened this issue Sep 9, 2022 · 1 comment · Fixed by #813
Labels
feature PPL Piped processing language v2.4.0 'Issues and PRs related to version v2.4.0'

Comments

@joshuali925
Copy link
Member

Is your feature request related to a problem?
PPL currently supports parse command that allows user to extract text from a field with regex pattern. But regex is difficult to write while many extracted patterns are likely to be existing patterns. Supporting grok can make this easier.

What solution would you like?
Allow extracting text using java-grok similar to current parse command.

What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.

Do you have any additional context?
Add any other context or screenshots about the feature request here.

@joshuali925 joshuali925 added the enhancement New feature or request label Sep 9, 2022
@penghuo
Copy link
Collaborator

penghuo commented Sep 9, 2022

I think we could add grok as a method in parse command.

  1. I feel adding a lots of command will confuse customer.
  2. If customer require grok command in future, we could add it later, there is no one way door.

@dai-chen dai-chen added PPL Piped processing language feature v2.4.0 'Issues and PRs related to version v2.4.0' and removed enhancement New feature or request labels Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature PPL Piped processing language v2.4.0 'Issues and PRs related to version v2.4.0'
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants