[ 
https://issues.apache.org/jira/browse/SOLR-18044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048883#comment-18048883
 ] 

ASF subversion and git services commented on SOLR-18044:
--------------------------------------------------------

Commit 0538d17e5ddb2a0f01bfe16884d1255c5fa45fb7 in solr's branch 
refs/heads/main from Gus Heck
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=0538d17e5dd ]

SOLR-18044 EssentialSolrRequestFilter to perform non-optional request wrapping 
operations  (#3997)



> Add universal request attributes in a servlet filter
> ----------------------------------------------------
>
>                 Key: SOLR-18044
>                 URL: https://issues.apache.org/jira/browse/SOLR-18044
>             Project: Solr
>          Issue Type: Sub-task
>            Reporter: Gus Heck
>            Assignee: Gus Heck
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> So far I've identified 3 attributes that are unconditionally set at various 
> points in SolrDispatchFilter and the constructor for HttpSolrCall. I believe 
> we can simplify that constructor and create a single place for setting up 
> attributes that are "always available". These attributes are:
>  # The tracer (key: REQ_ATTR_TRACING_TRACER )
>  # the RTimerTree (key: REQUEST_TIMER_SERVLET_ATTRIBUTE)
>  # the CoreContainer (key: org.apache.solr.CoreContainer)
> Other attributes that are set conditionally such as 
> `req.setAttribute("org.eclipse.jetty.multipartConfig", 
> multipartConfigElement);` probably can't move here so it's not possible to 
> corral a full view of what's in our request attributes, but this should 
> provide a clear place to add/identify attributes applicable to all requests.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to