[
https://issues.apache.org/jira/browse/SOLR-14067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269517#comment-17269517
]
ASF subversion and git services commented on SOLR-14067:
--------------------------------------------------------
Commit cf5db8d6513e0f3e556ab6ee1b9ad3a6472ad2f2 in lucene-solr's branch
refs/heads/master from Eric Pugh
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=cf5db8d ]
SOLR-14067: v3 Create /contrib/scripting module with ScriptingUpdateProcessor
(#2215)
* Creating Scripting contrib module to centralize the less secure code related
to scripts.
* tweak the changelog and update notice to explain why the name changed and the
security posture thinking
* the test script happens to be a currency.xml, which made me think we were
doing something specific to currency types, but instead any xml formatted file
will suffice for the test.
* drop the ing, and be more specific on the name of the ref guide page
* use the same name everywhere
Co-authored-by: David Smiley <[email protected]>
> 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: 6h 50m
> 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: [email protected]
For additional commands, e-mail: [email protected]