[
https://issues.apache.org/jira/browse/SOLR-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060826#comment-13060826
]
Erik Hatcher commented on SOLR-1280:
------------------------------------
In this update the config can be something like this:
{code}
<updateRequestProcessorChain name="fields_used" default="true">
<processor class="solr.processor.FieldsUsedUpdateProcessorFactory">
<str name="fieldsUsedFieldName">attribute_fields</str>
<str name="fieldNameRegex">.*_attribute</str>
</processor>
<processor class="solr.LogUpdateProcessorFactory" />
<processor class="solr.RunUpdateProcessorFactory" />
</updateRequestProcessorChain>
{code}
Regex was chosen to allow flexibility in matching field names for inclusion,
but I think perhaps a better (more easily comprehended/configured) way would be
to have a comma-separated list of field names that could contain a "*" for
globbing, which should be about all the flexibility needed for this.
> Fields used update processor
> ----------------------------
>
> Key: SOLR-1280
> URL: https://issues.apache.org/jira/browse/SOLR-1280
> Project: Solr
> Issue Type: New Feature
> Components: update
> Reporter: Erik Hatcher
> Priority: Trivial
> Attachments: FieldsUsedUpdateProcessorFactory.java,
> FieldsUsedUpdateProcessorFactory.java
>
>
> When dealing with highly heterogeneous documents with different fields per
> document, it can be very useful to know what fields are present on the result
> documents from a search. For example, this could be used to determine which
> fields make the best facets for a given query.
--
This message is automatically generated by JIRA.
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]
