[
https://issues.apache.org/jira/browse/SOLR-14067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17218643#comment-17218643
]
Chris M. Hostetter commented on SOLR-14067:
-------------------------------------------
IIRC the naming was chosen to try and make it clear that the Scrips had to be
stateless, and no state would be preserved from one request to another –
because that seemed very risky. ie: I don't think we were particularlay
anticipating a companion {{StatefulScriptingUpdateProcessor}} would come alone,
we were trying to make it clear to users (and future developers) that this
didn't support preserving state, and shouldn't in the future. (ie: "don't tweak
the engine behavior to make it stateful, it might break assumptions in existing
user scripts.")
At this point I have no particular feelings about renaming as long as the docs
are clear that it is stateless. (we had no ref-guide back then)
As for the backcompat question...
* if renaming only happens in 9.0 then i don't think backcompat is much of a
concern as far as the name goes.
* if the aim is for an 8.x release then i think a backcompat layer is important
** people shouldn't have to edit their solrconfig.xml files to upgrade a minor
release unless they want to take advantage of new functionality – existing
functionality should continue to work as is.
* by the same token: if the plan is to move to a contrib, then this shouldn't
happen until 9.0 (with or w/o a rename) so as to not break existing solr users.
> Deprecate StatelessScriptUpdateProcessor and disabled by default
> ----------------------------------------------------------------
>
> 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: 8.7
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> 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
