[
https://issues.apache.org/jira/browse/SOLR-10701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103471#comment-16103471
]
Andrey Kudryavtsev commented on SOLR-10701:
-------------------------------------------
I didn't get a part why there are all that static classes with tricky names to
store {{parentQuery}} to be later transformed into {{BitSetProducer}} instance
while {{ToChildBlockJoinQuery}} / {{ToParentBlockJoinQuery}} already have
{{BitSetProducer}} which just need to be exposed.
It is for some "Solr's only" caching magic or it is like legacy stuff?
> sort=parentfield(name,{!child}) asc
> -----------------------------------
>
> Key: SOLR-10701
> URL: https://issues.apache.org/jira/browse/SOLR-10701
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mikhail Khludnev
> Attachments: SOLR-10701.patch
>
>
> It's a twin-bro for SOLR-10521. When searching by {{\{!child}}} query we need
> to order kids by a parent field. {{sort=parentfield(name,$q) asc}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
