[
https://issues.apache.org/jira/browse/SOLR-14067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270459#comment-17270459
]
David Eric Pugh commented on SOLR-14067:
----------------------------------------
Hi all, so, not sure why I thought all the tests passed. Digging through the
errors, of course they failed.
I havne't done a revert before, waht is the best way to do this? Nervous
about making things worse!
Digging in:
With the ScriptingUpdateRequestProcessor moved to it's own contrib, it seems
like that the test for uploading configsets, where we check for the existence
of a script, needs the
org.apache.solr.scripting.update.ScriptingUpdateRequestProcessor, but of course
it's in a contrib. So I think I need to move the test out to the contrib
module, or figure out some sort of mock class.
I also had the ScriptUpdateProcessorFactory in the example TechProducts, to
enable one of the example commands in the Ref Guide page, somewhat similar to
the LTR Feature transformer. However, I clearly need to figure out how to get
the jars to work, or just remove it.
> 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 10m
> 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]
