[
https://issues.apache.org/jira/browse/SOLR-9657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15588598#comment-15588598
]
Noble Paul commented on SOLR-9657:
----------------------------------
Sorry about that [~dsmiley] , I should have responded to your comment and I
missed it. I'm fine with adding javadocs. Just that it was not clear as to
where you wanted it.
Is it to help a user who would use this URP? How many users of Solr are java
users and are likely to use javadocs. Most users rely on the the ref guide to
learn how to use a component. Honestly, a one liner is not really useful. You
really need a few examples at least to learn to use it.
Is it to help the Solr developer? I agree with you.
That being said . I'm not yet resolving this. There was a concern raised by
Erik hatcher about the variable naming
> 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
