You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Cassandra Targett (JIRA)" <ji...@apache.org> on 2018/01/31 19:14:00 UTC

[jira] [Updated] (SOLR-11775) json.facet can use inconsistent Long/Integer for "count" depending on shard count

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

Cassandra Targett updated SOLR-11775:
-------------------------------------
    Component/s: Facet Module

> json.facet can use inconsistent Long/Integer for "count" depending on shard count
> ---------------------------------------------------------------------------------
>
>                 Key: SOLR-11775
>                 URL: https://issues.apache.org/jira/browse/SOLR-11775
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Facet Module
>            Reporter: Hoss Man
>            Priority: Major
>
> (NOTE: I noticed this while working on a test for {{type: range}} but it's possible other facet types may be affected as well)
> When dealing with a single core request -- either standalone or a collection with only one shard -- json.facet seems to use "Integer" objects to return the "count" of facet buckets, however if the shard count is increased then the end client gets a "Long" object for the "count"
> (This isn't noticable when using {{wt=json}} but can be very problematic when trying to write client code using {{wt=xml}} or SolrJ



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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