-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[ML] find_structure_finder endpoint NPE risk with should_trim_fields #35462
Comments
Pinging @elastic/ml-core |
@webmat this is the bug you reported. |
droberts195
added a commit
to droberts195/elasticsearch
that referenced
this issue
Nov 12, 2018
The NPE would occur if should_trim_field was overridden to true and any field value was completely blank. This change defends against this situation. Fixes elastic#35462
droberts195
added a commit
that referenced
this issue
Nov 13, 2018
The NPE would occur if should_trim_field was overridden to true and any field value was completely blank. This change defends against this situation. Fixes #35462
droberts195
added a commit
that referenced
this issue
Nov 13, 2018
The NPE would occur if should_trim_field was overridden to true and any field value was completely blank. This change defends against this situation. Fixes #35462
droberts195
added a commit
that referenced
this issue
Nov 13, 2018
The NPE would occur if should_trim_field was overridden to true and any field value was completely blank. This change defends against this situation. Fixes #35462
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The ML
find_structure_finder
endpoint can fail with a null pointer exception ifshould_trim_fields
is overridden totrue
and there are blank fields in the delimited file.As an example to reproduce this:
where
PAN-sample.log
is a CSV file containing blank field values.The output is:
Stack trace is:
The text was updated successfully, but these errors were encountered: