[
https://issues.apache.org/jira/browse/SOLR-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-10521:
------------------------------------
Attachment: SOLR-10521.patch
[^SOLR-10521.patch] here we go!
the valuesource syntax is {{sort=childfield(field,$bjq) asc}} or
{{sort=childfield(field) asc}} assuming {{$q}}.
The sad thing is that, I cant' improve QueryComponent change (it's brilliant
already).
So, far it can be only used for sorting. But can be extended to regular value
source functionality in future. This might even work numerics, but I havent'
checked it yet.
Reviews and suggestions are urgently required!
> sort by string field of the nested child when searching with {!parent}
> ----------------------------------------------------------------------
>
> Key: SOLR-10521
> URL: https://issues.apache.org/jira/browse/SOLR-10521
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mikhail Khludnev
> Attachments: SOLR-10521.patch, SOLR-10521.patch, SOLR-10521-raw.patch
>
>
> The idea is to integrate Lucene's {{ToParentBlockJoinSortField}}
> The approach to hookup it is a little bit tricky:
> {{sort=\{!childfield bjq=$q field=COLOR_s}desc}}
> the question no.1 wdyt about the syntax?
> internally it creates a function query with valueSource which produces
> {{ToParentBlockJoinSortField}}
> The main challenge is picking Solr field type from
> {{ToParentBlockJoinSortField}}, because as-is it's broken on {{mergeIds}} -
> ByteRefs need to be properly marshared and unmarshalled by a field type from
> child scope.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
