[
https://issues.apache.org/jira/browse/SOLR-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-9448:
-----------------------------------
Description:
straightforward \[subquery] implementation executes requests on a caller
collection, but just hitting another one with
{{caller/select?q=..&collection=callee }}. The problem is that for
{{GET_FIELDS}} it uses uniqKey from a caller collection but not a callee one.
Another observation, at that case both single sharded collections are
collocated at the same instance. Then, subquery can't be parsed if it queries a
field which are absent in caller schema. All of this seems pretty strange like
hitting an edge case.
h2. workaround
Perhaps you can collocate secondary index and call it {{fromIndex=callee}}.
Or you can name uniqKey the same, keeping the different app semantic.
was:
straightforward \[subquery] implementation executes requests on a caller
collection, but just hitting another one with
{{caller/select?q=..&collection=callee }}. The problem is that for
{{GET_FIELDS}} it uses uniqKey from a caller collection but not a callee one.
h2. workaround
Perhaps you can collocate secondary index and call it {{fromIndex=callee}}.
Or you can name uniqKey the same, keeping the different app semantic.
> [subquery] can't pull fields from SolrCloud collection if it has a
> differently named uniqueKey
> ----------------------------------------------------------------------------------------------
>
> 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
>
> straightforward \[subquery] implementation executes requests on a caller
> collection, but just hitting another one with
> {{caller/select?q=..&collection=callee }}. The problem is that for
> {{GET_FIELDS}} it uses uniqKey from a caller collection but not a callee one.
> Another observation, at that case both single sharded collections are
> collocated at the same instance. Then, subquery can't be parsed if it queries
> a field which are absent in caller schema. All of this seems pretty strange
> like hitting an edge case.
> h2. workaround
> Perhaps you can collocate secondary index and call it {{fromIndex=callee}}.
> Or you can name uniqKey the same, keeping the different app semantic.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
