lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (Commented) (JIRA) <>
Subject [jira] [Commented] (SOLR-2599) FieldCopy Update Processor
Date Wed, 05 Oct 2011 18:26:29 GMT


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}}
> FieldCopy Update Processor
> --------------------------
>                 Key: SOLR-2599
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message