[
https://issues.apache.org/jira/browse/SOLR-10610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16097621#comment-16097621
]
Jason Gerlowski commented on SOLR-10610:
----------------------------------------
{noformat}
+ // TODO: actually perform the query
+ LOG.info("Processing {}", rb.req);
+ // TODO: Sample simple check that can be performed on the query
+ if (rb.getQueryString().length() > 10) {
+ rb.setCanaryStatus(CanaryStatus.STATUS_FAILURE);
+ } else {
+ rb.setCanaryStatus(CanaryStatus.STATUS_SUCCESS);
+ }
{noformat}
So, to clarify the proposal, is the idea that success/failure comes from:
- static checks done on the query (length, num clauses, num fields, wildcards)?
- the results of running the query on 1 or more canary replicas?
- or some combination of both?
> Add CanaryComponent, a search component to analyse requests
> -----------------------------------------------------------
>
> Key: SOLR-10610
> URL: https://issues.apache.org/jira/browse/SOLR-10610
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Domenico Fabio Marino
> Priority: Minor
> Attachments: SOLR-10610.patch
>
>
> This patch outlines a new component that analyses a request and reports
> whether it is too complex to continue processing.
> Running this component should be conditional and happen before other
> components start processing. The component will set a status flag so that
> other components can know the result of the Canary check, and also adds some
> information to the response sent back to the client.
> The component runs the query on the set of replicas that are tagged with the
> "canary" tag.
> Please note this is only an outline so far and it therefore lacks test cases.
> When this will be more feature-complete, a test case will be added
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
