[
https://issues.apache.org/jira/browse/SOLR-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev resolved SOLR-9448.
------------------------------------
Resolution: Workaround
Fix Version/s: 6.4
master (7.0)
> [subquery] calls another collection fails with "undefined field" or NPE from
> mergeIds
> -------------------------------------------------------------------------------------
>
> Key: SOLR-9448
> URL: https://issues.apache.org/jira/browse/SOLR-9448
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 6.1, 6.2
> Reporter: Mikhail Khludnev
> Assignee: Mikhail Khludnev
> Fix For: master (7.0), 6.4
>
> Attachments: SOLR-9448.patch, SOLR-9448.patch, SOLR-9448.patch,
> SOLR-9448.patch
>
>
> If subquery collection has a different unique key field name (let's say
> {{foo_id}} is different to {{id}} in primary collection), you've got
> {{NullPoniterException}} from {{QueryComponent.mergeIds()}}. To accommodate
> the difference between uniqueKey field names between collections, add the
> following parameters {{foo.fl=id:foo_id&foo.distrib.singlePass=true}}. The
> former one renames uniqueKey field, the later switches to single pass search.
> There is no way to rename field in default processing.
> In a rare case when a collection under subquery has no unqueKey at all, it
> leads to something like "undefined field", but it's not going to work anyway.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
