[
https://issues.apache.org/jira/browse/SOLR-14067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220124#comment-17220124
]
David Smiley commented on SOLR-14067:
-------------------------------------
RE package: That will happen in SOLR-14688 or some new sub-task ticket of that.
I think we shouldn't name this contrib "scripting-update-processor"; I think it
should just be "scripting" to make room for other scripting functionality. The
URP may be the only component there on inception, but it's easy to imagine
other things being added. XSLT belongs there. WDYT?
I disagree on use of the "@Deprecation" annotation (although the
{{\@deprecated}} javadoc tag is fine) because the user will get a generic
warning about the functionality being deprecated (implying you shouldn't use
it). Instead, use the new DeprecationLog utility in the constructor to say
something more helpful. Or just don't bother, as you wish.
> Move StatelessScriptUpdateProcessor to a contrib
> ------------------------------------------------
>
> Key: SOLR-14067
> URL: https://issues.apache.org/jira/browse/SOLR-14067
> Project: Solr
> Issue Type: Improvement
> Reporter: Ishan Chattopadhyaya
> Assignee: David Eric Pugh
> Priority: Major
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Move server-side scripting out of core and into a new contrib. This is
> better for security.
> Former description:
> ----
> We should eliminate all scripting capabilities within Solr. Let us start with
> the StatelessScriptUpdateProcessor deprecation/removal.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
