[ https://issues.apache.org/jira/browse/SOLR-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455666#comment-13455666 ]
Bertjan Broeksema commented on SOLR-2782: ----------------------------------------- Noticed this issue as well. Seeing that this bug is over a year old already, any news on this? Is anybody taking this up? > Parameter inconsistency in SolrJ: ints versus longs > --------------------------------------------------- > > Key: SOLR-2782 > URL: https://issues.apache.org/jira/browse/SOLR-2782 > Project: Solr > Issue Type: Bug > Components: clients - java > Affects Versions: 3.3 > Reporter: Willis Blackburn > Priority: Minor > > I've noticed that SolrDocumentsList uses long for fields like numFound and > start. But the methods SolrQuery.setRows and setStart only accept ints, > which leads to the possibility of a query being unable to request some of the > documents found by a query. I realize that this is an edge case, since not > many Lucene indexes will have 2 billion+ documents? But it is an > inconsistency and requires that I at some point reduce a long to an int in > code, which always feels wrong. -- 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: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org