Currently the mapped field plugin returns a single value. It might be handy to support multiple values, e.g. where a mapped field token joins term parents using a delimiter.
Attached patch allows exploding a mapped field value into an array based on a delimiter. I wasn't sure what delimiter to use, since it should be something that isn't likely to be present in the content unless intentionally placed there. At the moment it uses a double semicolon ';;'.
| Comment | File | Size | Author |
|---|---|---|---|
| search_api_field_map-support_multiple_values.patch | 1.22 KB | bgilhome |
Comments
Comment #2
agentrickardI would think that we need a separate field processor for this, since is_list would make all such fields multivalue, which is not desired.
Creating multivalue fields can cause issues on indexing if the base field definition expects a string. You end up with Solr expecting a ts_* field and being handed a tm_* field, which throws a fatal error.