[
https://issues.apache.org/jira/browse/SOLR-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121327#comment-13121327
]
Jan Høydahl commented on SOLR-2599:
-----------------------------------
Perhaps {{multival}} should be renamed {{multiValued}} to comply with schema
lingo?
Also, if I make it (optionally) schema aware, I can set {{multiValued}}
behavior as default if {{dest}} field is multivalued. Also, perhaps it makes
sense to allow {{append}} for {{multiValued}} as well, and let it append all
{{source}} fields to a string, and then adding this concatenated string as one
single field value instead of each {{source}} as its own value?
The reason I want to be able to disable strict schema checking is in the case
where a processor creates intermediate fields only, which we know will be
removed from {{SolrInputDocument}} before indexing, so that we can be free to
name it whatever we like without causing an error. Unfortunately,
{{ExtractingRequestHandler}} is too strict here and would benefit from a
{{enforceSchema=false}} option.
> FieldCopy Update Processor
> --------------------------
>
> Key: SOLR-2599
> URL: https://issues.apache.org/jira/browse/SOLR-2599
> Project: Solr
> Issue Type: New Feature
> Components: update
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Attachments: SOLR-2599.patch
>
>
> Need an UpdateProcessor which can copy and move fields
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
