[
https://issues.apache.org/jira/browse/SOLR-18049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048265#comment-18048265
]
David Smiley commented on SOLR-18049:
-------------------------------------
Instead of being a dedicated issue, isn't it enough for javadocs on each filter
to say something when those issues/PRs are implemented? And/or a comment in
web.xml.
I think it's too internal of a matter to touch the ref guide.
> Document which filters are critical
> -----------------------------------
>
> Key: SOLR-18049
> URL: https://issues.apache.org/jira/browse/SOLR-18049
> Project: Solr
> Issue Type: Sub-task
> Reporter: Gus Heck
> Priority: Major
>
> Once we have pulled out various functionality into filters, we should develop
> a clear notion of which filters are critical and cannot be removed and which
> ones might be removed, or replaced with alternate implementations.
> Of course with enough effort anything could be replaced, by folks customizing
> solr, but what we want to denote is "easy/intended" vs "hard/expert"
> My initial guess is:
> Required:
> * path exclusion, (unless one is removing the UI?)
> * MDC setup
> * Request attributes/globals
> Pluggable:
> * Rate Limiting
> * Tracing (removal if never going to use, or variations in execution
> details, using the same tracing library)
> * Auth (making this pluggable is key).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
