Ingest UI Pattern Review Screen #5892
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <div class="wizard-step-title"> | ||
| <h3>Review the index pattern</h3> | ||
| Here we'll define how and where to store your parsed events. We've made some intellient guesses for you, but most | ||
| fields can be changed iw we got it wrong! |
There was a problem hiding this comment.
iw we got it wrong --> if we got it wrong?
|
Thanks for taking a look @michaelcheng429 |
|
Sorting on the type column, |
| knownFieldTypes[field] = 'geo_point'; | ||
| } | ||
| else if (processor.date) { | ||
| const field = processor.date.target_field || '@timestamp'; |
There was a problem hiding this comment.
should there be any target_field conflict checking on the front end? do you know if this is handled on the server?
There was a problem hiding this comment.
The ES ingest API simply overwrites the target_field if it already exists, so I don't think we have to worry about conflicts.
| this.rows = _.map(this.indexPattern.fields, (field) => { | ||
| const sampleValue = this.sampleDocs[field.name]; | ||
| return [ | ||
| field.name, |
There was a problem hiding this comment.
Great catch, updated it and I think I covered everything
|
Looking good! Made some comments, passing back. |
|
@jbudz made some updates and left some follow up comments, let me know how it looks now. |
|
LGTM |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Requires #5790. When reviewing this pull, you can ignore the changes from that PR which have been merged in.
Implements the pattern review step from #5974. Takes the pipeline and example docs from the previous step and creates an simple index pattern with a title, time_field_name (if a date field is present), and fields with auto detected types. The user can configure the index pattern we've generated. The result of the step is an index pattern object that can be sent to the new ingest API #5199 once the user clicks save (to be implemented in a coming PR).
This PR works with some hard coded test data which will be removed once all of the wizard steps have been merged into the feature/ingest branch and wired together.