janhoy commented on a change in pull request #372:
URL: https://github.com/apache/solr/pull/372#discussion_r746157330
##########
File path: solr/core/src/java/org/apache/solr/handler/RequestHandlerBase.java
##########
@@ -51,9 +52,10 @@
import static org.apache.solr.core.RequestParams.USEPARAM;
/**
- *
+ * Base class for all request handlers.
*/
-public abstract class RequestHandlerBase implements SolrRequestHandler,
SolrInfoBean, NestedRequestHandler, ApiSupport {
+public abstract class RequestHandlerBase implements
Review comment:
> So does the Schema screen requires "read" to show the screen? That's
an interesting screen... it can expose data in terms of field values in term
statistics but otherwise it's mostly a "config-read" tool. I don't recall how
this screen maps to handlers.
I just checked what end points are queried when clicking around in the UI.
Turns out that the collection-read and core-read are always queried to fill the
collection/core dropdowns. It should of course as a SPA remember the values and
not re-query every time, but I did not dive in to try to fix that.
The Schema screen uses Luke, and Luke requires the READ permission. I think
it fetches all field names etc from luke as well, so the screen would be pretty
useless without access to Luke.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
