Support optional params for all processors; onboard text_chunking processor #265
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.
Description
This PR enables a pre-configured set of optional parameters for each processor type, all under an
Advanced settings
accordion. It also adds the text chunking processor as an available option for ingest.More details:
optionalFields
field for each processor configTextChunkingProcessorInputs
due to its complexity; we display a different set of optional fields based on the selected text chunking algorithm. Also adds special logic inconfig_to_template_utils
to only add any configured optional fields relevant to the currently selected algorithm.boolean
andnumber
fields as optional config field typescamelCaseToTitleString()
helper fn and removes thelabel
field in the config to help minimize what we persist on-cluster. We can now just generate the field title based on its ID.Demo video (existing processors with optional fields):
screen-capture.19.webm
Demo video (new text chunking ingest processor):
screen-capture.20.webm
Issues Resolved
Makes progress on #23
Makes progress on #219
Check List
--signoff
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.