[jira] [Commented] (SOLR-9657) Create a new TemplateUpdateProcessorFactory
[
https://issues.apache.org/jira/browse/SOLR-9657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15587696#comment-15587696
]
Noble Paul commented on SOLR-9657:
--
The plan is to have automatic request parameter support for all URPs (wherever
possible)
> Create a new TemplateUpdateProcessorFactory
> ---
>
> 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=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
[jira] [Commented] (SOLR-9657) Create a new TemplateUpdateProcessorFactory
[
https://issues.apache.org/jira/browse/SOLR-9657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15587655#comment-15587655
]
Ishan Chattopadhyaya commented on SOLR-9657:
+1 to this URP (since it takes request parameters for fields).
> Create a new TemplateUpdateProcessorFactory
> ---
>
> 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=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
[jira] [Commented] (SOLR-9657) Create a new TemplateUpdateProcessorFactory
[
https://issues.apache.org/jira/browse/SOLR-9657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15587525#comment-15587525
]
Noble Paul commented on SOLR-9657:
--
bq.I wonder if it's feasible for the URP processing subsystem to be refactored
such that all URPs could operate in both modes, similarly to how request
handlers can be
That's the plan
> Create a new TemplateUpdateProcessorFactory
> ---
>
> 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=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
[jira] [Commented] (SOLR-9657) Create a new TemplateUpdateProcessorFactory
[
https://issues.apache.org/jira/browse/SOLR-9657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15587518#comment-15587518
]
David Smiley commented on SOLR-9657:
This is nice; it'd come in handle for "lat,lon". Can you add at least a
one-liner javadoc to the class? And I like that this can work off of Solr
request parameters but why doesn't it _also_ work like all the other ones work
-- by predefined configuration in solrconfig.xml? I wonder if it's feasible
for the URP processing subsystem to be refactored such that *all* URPs could
operate in both modes, similarly to how request handlers can be. It'd be great
to not have this inconsistency.
> Create a new TemplateUpdateProcessorFactory
> ---
>
> 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=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
