You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2020/05/21 14:35:00 UTC

[jira] [Assigned] (SOLR-14384) Stack SolrRequestInfo

     [ https://issues.apache.org/jira/browse/SOLR-14384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Smiley reassigned SOLR-14384:
-----------------------------------

    Assignee: David Smiley
    Reporter: David Smiley  (was: Mikhail Khludnev)

> Stack SolrRequestInfo
> ---------------------
>
>                 Key: SOLR-14384
>                 URL: https://issues.apache.org/jira/browse/SOLR-14384
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: David Smiley
>            Assignee: David Smiley
>            Priority: Minor
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Sometimes SolrRequestInfo need to be suspended/overridden with a new one that is used temporarily. Examples are in the {{[subquery]}} transformer, and in warm of caches, and in QuerySenderListener (another type of warming), maybe others.  This can be annoying to do correctly, and in at least one place it isn't done correctly.  SolrRequestInfoSuspender shows some complexity.  In this issue, [~dsmiley] proposes using a stack internally to SolrRequestInfo that is push'ed and pop'ed.  It's not the only way to solve this but it's one way.
>  See linked issues for the context and discussion.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org