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 far: /stream?explain=true&expr=search(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 clause Is my syntax wrong or do I need to enable schema or config level changes in order to get this work? On Fri, Jun 28, 2019 at 11:50 AM Erick Erickson <erickerick...@gmail.com> wrote: > 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 export would leave off the last > packet IIRC, what version of Solr are you using? > > Best, > Erick > > > On Jun 28, 2019, at 7:11 AM, Kudrettin Güleryüz <kudret...@gmail.com> > wrote: > > > > 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 the numFound value was different > > between these two queries for the same core > > export?fl=id&q=*:*&sort=id%20desc > > select?fl=id&q=*:*&sort=id%20desc > > > > Can you please explain why this may be the case? Also any suggestions on > > alternatives would be nice. > > > > Thank you > >
