[
https://issues.apache.org/jira/browse/SOLR-14067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17273169#comment-17273169
]
David Eric Pugh commented on SOLR-14067:
----------------------------------------
I've dug into the unit test failures, and I think I've sorted them out. One
big question.. TestConfigSetsAPI has some tests around the trusted/untrusted
config sets. One of those is a test of the scripting update processor.
Instead of moving that test OVER to the /contrib/scripting, I instead added a
\{{MockScriptUpdateProcessorFactory}} that behaves the same as the
{{ScriptUpdateProcessorFactory}} as far as the config test trust/untrust goes.
[https://github.com/apache/lucene-solr/pull/2257/commits/f39cb8e37efa51fe12b80901fce035282b4d8543]
has this change. Thoughts on this approach?
> 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
> Fix For: master (9.0)
>
> Time Spent: 7h 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
