You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/03/19 17:11:38 UTC
[jira] [Commented] (SOLR-7262) Registering / changing request
handlers not thread safe
[ https://issues.apache.org/jira/browse/SOLR-7262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369614#comment-14369614 ]
ASF subversion and git services commented on SOLR-7262:
-------------------------------------------------------
Commit 1667799 from [~yonik@apache.org] in branch 'dev/trunk'
[ https://svn.apache.org/r1667799 ]
SOLR-7262: fix broken thread safety for request handler registry introduced by SOLR-7073
> Registering / changing request handlers not thread safe
> -------------------------------------------------------
>
> Key: SOLR-7262
> URL: https://issues.apache.org/jira/browse/SOLR-7262
> Project: Solr
> Issue Type: Bug
> Reporter: Yonik Seeley
> Attachments: SOLR-7262.patch
>
>
> Here's part of the javadoc for RequestHandlers.register()
> {code}
> * This call is thread safe.
> *
> * @return the previous handler at the given path or null
> */
> public SolrRequestHandler register( String handlerName, SolrRequestHandler handler ) {
> {code}
> But looking at the changes from SOLR-7073, this is clearly not the case (it's no longer thread safe). Was this thread safety removed on purpose or was it accidental?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org