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

Russell Black commented on SOLR-3195:
-------------------------------------

Martijn, 

There is one thing I'd like your opinion on -- for distributed grouping the 
first phase and second phase are given the full time allotment with my patch, 
essentially resulting in doubling the effect of the timeAllowed parameter.  Do 
you think we should try to be smarter about it?  We could subtract the time 
time of the first query from the timeAllowed parameter that gets handed to the 
second query, resulting in more accurate overall time.  

What do you think?
                
> timeAllowed is ignored for grouping queries
> -------------------------------------------
>
>                 Key: SOLR-3195
>                 URL: https://issues.apache.org/jira/browse/SOLR-3195
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 3.5, 4.0
>            Reporter: Russell Black
>            Assignee: Martijn van Groningen
>              Labels: patch
>         Attachments: SOLR-3195-timeallowed-for-grouping.patch
>
>
> For grouping queries, the {{timeAllowed}} parameter is ignored.  I couldn't 
> find this limitation documented anywhere, and we would like to use that 
> feature in our production system.  I have created a patch that makes grouping 
> queries respect the {{timeAllowed}} parameter.  The test cases all pass, and 
> it and it seems to work well.  I added support for both distributed and 
> non-distributed grouping.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Reply via email to