lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomás Fernández Löbbe (JIRA) <>
Subject [jira] [Updated] (SOLR-4175) SearchComponent chain can't contain two components of the same class and use debugQuery
Date Thu, 13 Dec 2012 15:38:12 GMT


Tomás Fernández Löbbe updated SOLR-4175:

    Attachment: SOLR-4175.patch

I'm attaching a possible fix. The SearchComponent class now uses the name defined in the solrconfig.xml
(or the default component name for the default ones).
This will change the debugQuery output, the "timing section" will use those names instead
of the class names, like:

 <lst name="timing">
    <double name="time">2.0</double>
    <lst name="prepare">
      <double name="time">0.0</double>
      <lst name="query">
        <double name="time">0.0</double>
      <lst name="facet">
        <double name="time">0.0</double>
      <lst name="mlt">
        <double name="time">0.0</double>
      <lst name="highlight">
        <double name="time">0.0</double>
      <lst name="stats">
        <double name="time">0.0</double>
      <lst name="debug">
        <double name="time">0.0</double>
It will also change the MBean names.


> SearchComponent chain can't contain two components of the same class and use debugQuery
> ---------------------------------------------------------------------------------------
>                 Key: SOLR-4175
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.0
>            Reporter: Tomás Fernández Löbbe
>            Priority: Minor
>         Attachments: failure.patch, SOLR-4175.patch
> steps to reproduce the issue:
> 1) Add two components of the same type to the components chain of the request handler
> 2) start solr with assertions enabled
> 3) run a query to the request handler configured in 1 with debugQuery=true
> The query will throw a java.lang.AssertionError. I'll attach a test case to reproduce
the issue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message