Re: different numFound value /select vs. /export

Thank you, issue was indeed format error. On Fri, Jun 28, 2019 at 2:23 PM Colvin Cowie wrote: > */stream?explain=true=sear* > > > *ch(myCore,zkHost=”192.168.1.10:2181 > ",qt=”/export”,q=”*:*”, fl=”id”,sort=”id asc”) > returns* > *

Re: different numFound value /select vs. /export

*/stream?explain=true=sear* *ch(myCore,zkHost=”192.168.1.10:2181 ",qt=”/export”,q=”*:*”, fl=”id”,sort=”id asc”) returns* * 'search(myCore,zkHost=”192.168.1.10:2181 \",qt=”/export”,q=”** *:*”, fl=”id”,sort=”id asc”)' is not a proper expression

Re: different numFound value /select vs. /export

Thank you for responding. I didn't go though the parsers involved, I assume they'd be the defaults. I did notice later, though that /export is core specific. In fact we have a Solr Cloud with 6 shards. I also found out that /stream can be used for this but couldn't get a solution that works so

Re: different numFound value /select vs. /export

First I’d make sure that you were using the same query parser in both situations. Second, export is specific to a core, it is not cloud-aware so if this is SolrCloud I’d expect major differences, which you haven’t told us about, off by 5? 10,000?. Third, there was a bug at one point where

different numFound value /select vs. /export

Hi, I'd like to give my website users ability to export a field for the full search result set. Specifying a very large pageSize seems to perform very poorly for this purpose. Therefore, considering using export requestHandler for exporting search results. When I play with a core, I noticed that