lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Lucey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-6037) Stats Component Reports Incorrect Max in Distributed Data
Date Thu, 01 May 2014 14:42:15 GMT

     [ https://issues.apache.org/jira/browse/SOLR-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Lucey updated SOLR-6037:
------------------------------

    Description: 
When computing statistics using the statistics component, the value for max may be reported
incorrectly if the maximum value does not lie in the first shard. 

This is where the problem is (in StatsValuesFactory.java):
{{
  @Override
  protected void updateMinMax(Date min, Date max) {
    if(this.min==null || this.min.after(min)) {
      this.min = min;
    }
    if(this.max==null || this.max.before(min)) {
      this.max = max;
    }
  }
}}
Attached is a one-line patch which fixes this issue.

  was:
When computing statistics using the statistics component, the value for max may be reported
incorrectly if the maximum value does not lie in the first shard. 

This is where the problem is (in StatsValueFactory.java):
  @Override
  protected void updateMinMax(Date min, Date max) {
    if(this.min==null || this.min.after(min)) {
      this.min = min;
    }
    if(this.max==null || this.max.before(min)) {
      this.max = max;
    }
  }

Attached is a one-line patch which fixes this issue.


> Stats Component Reports Incorrect Max in Distributed Data
> ---------------------------------------------------------
>
>                 Key: SOLR-6037
>                 URL: https://issues.apache.org/jira/browse/SOLR-6037
>             Project: Solr
>          Issue Type: Bug
>          Components: SearchComponents - other
>    Affects Versions: 5.0
>            Reporter: Brett Lucey
>            Priority: Minor
>         Attachments: SOLR-6037.patch
>
>
> When computing statistics using the statistics component, the value for max may be reported
incorrectly if the maximum value does not lie in the first shard. 
> This is where the problem is (in StatsValuesFactory.java):
> {{
>   @Override
>   protected void updateMinMax(Date min, Date max) {
>     if(this.min==null || this.min.after(min)) {
>       this.min = min;
>     }
>     if(this.max==null || this.max.before(min)) {
>       this.max = max;
>     }
>   }
> }}
> Attached is a one-line patch which fixes this issue.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message