This repository was archived by the owner on Nov 7, 2018. It is now read-only.
Support multivalue fields #317
Open
Conversation
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR introduces a new field type of
multivalueto allow for csv columns that have multiple values in one field. By specifying in the data.yaml thetype: 'multivalue', the importer will parse a string value with a comma separated list (default) into an array and save the field. You may also provide a optionalseparatorkey to specify a different delimiter other than the default comma. This is modeld after the elasticsearch multivalue field and adds aposition_offset_gapto each field value to avoid slop results.Adding multi-value field support should help prepare for: RTICWDT/college-scorecard#187