[
https://issues.apache.org/jira/browse/SOLR-7683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602228#comment-14602228
]
Gregory Chanan commented on SOLR-7683:
--------------------------------------
Does the request type have to be a string? Seems cleaner to just use the enum
and have the client code transform the enum to a string when it needs to send
it. Or are you worried about being able to extend the types without modifying
solr (i.e. I implement my own request handler that sends its own types that I
want in their own pool -- can I do that?)
Also, it sure would be nice to be able to be able to specify some kind of
enforcement...seems like a mailicious user could just mess with type
context/type to make this ineffectual, e.g. send everything as an internal
request. Any idea how this could be handled?
> Introduce support to identify Solr internal request types
> ---------------------------------------------------------
>
> Key: SOLR-7683
> URL: https://issues.apache.org/jira/browse/SOLR-7683
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Reporter: Hrishikesh Gadre
> Attachments: SOLR-7683.patch
>
>
> SOLR-7344 is introducing support to partition the Jetty worker pool to
> enforce the number of concurrent requests for various types (e.g.
> Internal_Querying, Internal_Indexing, External etc.). For this we need to
> identify requests sent between Solr servers and their types (i.e.
> Querying/Indexing etc.).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
