Susmit:
re: the second bug:
bq: I ran into another issue - if data in any of the shards is empty, export
throws an error-
This sounds like something that may be already fixed in SOLR-9187
(just committed yesterday). Would it be possible to check a new build?
I ran across this largely by chance w
Yeah, it sounds like we've got two good bugs here. Feel free to create jira
tickets for them, I don't believe they've been created yet. It would be
good to get these fixed for the next release.
Joel Bernstein
http://joelsolr.blogspot.com/
On Fri, Jun 10, 2016 at 7:25 PM, Susmit Shukla
wrote:
>
Hi Joel,
I would need to join results from 2 solr clouds before collapsing so it
would not be an issue right now.
I ran into another issue - if data in any of the shards is empty, export
throws an error-
Once i have atleast one document in each shard, it works fine.
org.apache.solr.common.SolrExc
This sounds like a bug. I'm pretty sure there are no tests that use
collapse with the export handler.
Joel Bernstein
http://joelsolr.blogspot.com/
On Fri, Jun 10, 2016 at 3:59 PM, Susmit Shukla
wrote:
> Hi,
>
> I'm running this export query, it is working fine. f1 is the uniqueKey and
> running
Hi,
I'm running this export query, it is working fine. f1 is the uniqueKey and
running solr 5.3.1
/export?q=f1:term1&sort=f1+desc&fl=f1,f2
if I add collapsing filter, it is giving NullPointerException
/export?q=f1:term1&sort=f1+desc&fl=f1,f2&fq={!collapse field=f2}
does collapsing filter work
