[ https://issues.apache.org/jira/browse/SOLR-9657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15588626#comment-15588626 ]
David Smiley commented on SOLR-9657: ------------------------------------ Fair point RE refguide. Nevertheless, IMO as a matter of universal good developer practices I think *every* top-level non-test class ought to have _at least one sentence said about it_, aimed at any other developer (whoever they may be) stumbling over it -- either via looking at the actual source, or via docs pop-up in their IDE. IMO it's a shame the Solr codebase has gotten to the point that so little has such a bare minimum. For this one I'll write it for you; feel free to edit: "Adds new fields to documents based on a template pattern specified via template.field request parameters (multi-valued)." [~arafalov] do you think this is at all useful? I know you work on adding docs to URPs 'n things. > Create a new TemplateUpdateRequestProcessorFactory > -------------------------------------------------- > > Key: SOLR-9657 > URL: https://issues.apache.org/jira/browse/SOLR-9657 > Project: Solr > Issue Type: New Feature > Security Level: Public(Default Security Level. Issues are Public) > Reporter: Noble Paul > Assignee: Noble Paul > Attachments: SOLR-9657.patch > > > Unlike other URPs, this will operate on request parameters > example: > {code} > processor=Template&Template.field=fname:${somefield}some_string${someotherfield} > {code} > The actual name of the class is {{TemplateUpdateProcessorFactory}} and it is > possible to optionally drop the {{UpdateProcessorfactory}} part. The > {{Template.field}} specifies a field name as well as a template. The > {{Template.field}} parameter is multivalued , so , it is possible to add > multiple fields or a multivalued field with same name -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org