[
https://issues.apache.org/jira/browse/SOLR-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677849#comment-13677849
]
Steve Rowe commented on SOLR-4893:
----------------------------------
bq. I think that covers your comments?
Oops, I missed one:
bq. my preference would be to leave a deprecated version of the old
createFieldNameSelector that delegates to your new version
I went to do this and noticed two things: a) it's marked with @lucene.internal;
and b) in order to support the new selector parameter
{{fieldNameMatchesSchemaField}}, we'd have to change the signature on the
original version anyway. So since it's going to break users' compilation
either way, I don't it's worth it to keep the old version. (I guess we could
keep the old version without the new selector parameter, and fill in null for
it when passing to the new version, but I'd rather people have to deal with the
new parameter.)
> Add a FieldMutatingUpdateProcessor FieldNameSelector that checks whether a
> field matches any schema field
> ----------------------------------------------------------------------------------------------------------
>
> Key: SOLR-4893
> URL: https://issues.apache.org/jira/browse/SOLR-4893
> Project: Solr
> Issue Type: Improvement
> Components: update
> Reporter: Steve Rowe
> Assignee: Steve Rowe
> Priority: Minor
> Attachments: SOLR-4893.patch, SOLR-4893.patch, SOLR-4893.patch
>
>
> Add a new field update processor selector that will configure the processor
> to select fields that match any schema field, or that don't match any schema
> field, depending on its boolean parameter, e.g. to select fields that don't
> match any schema field:
> {code:xml}
> <bool name="fieldNameMatchesSchemaField">false</bool>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]