[
https://issues.apache.org/jira/browse/SOLR-13318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16871679#comment-16871679
]
Jason Gerlowski commented on SOLR-13318:
----------------------------------------
Thanks for bringing this up again.
It probably still makes sense to backport. I'm not sure what the odds of a
7.7.3 release are, but the effort required to backport this is low, and if one
occurs, it would be nice to offer this fix to people in it.
I can put it on my todo list for this week, and will make sure I follow up this
time.
> JsonFacetingResponse classes should record provide access to count fields as
> longs
> -----------------------------------------------------------------------------------
>
> Key: SOLR-13318
> URL: https://issues.apache.org/jira/browse/SOLR-13318
> Project: Solr
> Issue Type: Bug
> Components: SolrJ
> Affects Versions: 7.7.1
> Reporter: Jason Gerlowski
> Assignee: Jason Gerlowski
> Priority: Minor
> Attachments: SOLR-13318-branch_8x.patch, SOLR-13318.patch,
> SOLR-13318.patch
>
>
> JsonFacetingResponse and its series of dependent classes hold a variety of
> count fields for bucket counts and various optional properties
> ({{allBuckets}}, {{numBuckets}}, etc.). Currently, some of the code that
> parses these values out of the originating NamedList either stores or casts
> the values as ints. When doc counts are low this works fine. But when the
> doc counts become larger and stray into "long" territory, SolrJ is liable to
> blow up with ClassCastExceptions.
> A user on the list reported on of these with the partial stack trace:
> {code}
> Caused by: java.lang.ClassCastException: java.lang.Long cannot be cast to
> java.lang.Integer
> at
> org.apache.solr.client.solrj.response.json.NestableJsonFacet.<init>(NestableJsonFacet.java:52)
> at
> org.apache.solr.client.solrj.response.QueryResponse.extractJsonFacetingInfo(QueryResponse.java:200)
> at
> org.apache.solr.client.solrj.response.QueryResponse.getJsonFacetingResponse(QueryResponse.java:571)
> {code}
> We should fix this so that these classes can be used without incident for any
> doc counts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]