[
https://issues.apache.org/jira/browse/SOLR-8208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223511#comment-15223511
]
Mikhail Khludnev edited comment on SOLR-8208 at 4/3/16 8:49 PM:
----------------------------------------------------------------
it seems like param tracing can be done with {{logParamsList}}
{noformat}
...Request [collection1] webapp=null path=null
params={q=name_s:dave&subq1.rows=6&indent=true&fl=*,depts:[subquery+prefix%3Dsubq1+]&rows=2&subq1.indent=true&subq1.logParamsList=q,fl,rows,subq1.row.dept_ss_dv&wt=xml&subq1.fl=text_t&subq1.q={!terms+f%3Ddept_id_s+v%3D$subq1.row.dept_ss_dv+separator%3D,}}
hits=2 status=0 QTime=9979
...Request [collection1] webapp=null path=null
params={q={!terms+f%3Ddept_id_s+v%3D$subq1.row.dept_ss_dv+separator%3D,}&subq1.row.dept_ss_dv=Support,Engineering&fl=text_t&rows=6}
hits=6 status=0 QTime=60740
{noformat}
was (Author: mkhludnev):
it seems like param tracing can be done with {{logParamsList}}
{quote}
...Request [collection1] webapp=null path=null
params={q=name_s:dave&subq1.rows=6&indent=true&fl=*,depts:[subquery+prefix%3Dsubq1+]&rows=2&subq1.indent=true&subq1.logParamsList=q,fl,rows,subq1.row.dept_ss_dv&wt=xml&subq1.fl=text_t&subq1.q={!terms+f%3Ddept_id_s+v%3D$subq1.row.dept_ss_dv+separator%3D,}}
hits=2 status=0 QTime=9979
...Request [collection1] webapp=null path=null
params={q={!terms+f%3Ddept_id_s+v%3D$subq1.row.dept_ss_dv+separator%3D,}&subq1.row.dept_ss_dv=Support,Engineering&fl=text_t&rows=6}
hits=6 status=0 QTime=60740
{quote}
> DocTransformer executes sub-queries
> -----------------------------------
>
> Key: SOLR-8208
> URL: https://issues.apache.org/jira/browse/SOLR-8208
> Project: Solr
> Issue Type: Improvement
> Reporter: Mikhail Khludnev
> Assignee: Mikhail Khludnev
> Labels: features, newbie
> Attachments: SOLR-8208.diff, SOLR-8208.patch, SOLR-8208.patch,
> SOLR-8208.patch, SOLR-8208.patch, SOLR-8208.patch, SOLR-8208.patch,
> SOLR-8208.patch, SOLR-8208.patch
>
>
> The initial idea was to return "from" side of query time join via
> doctransformer. I suppose it isn't query-time join specific, thus let to
> specify any query and parameters for them, let's call them sub-query. But it
> might be problematic to escape subquery parameters, including local ones,
> e.g. what if subquery needs to specify own doctransformer in &fl=\[..\] ?
> I suppose we can allow to specify subquery parameter prefix:
> {code}
> ..&fl=id,[subquery paramPrefix=subq1.
> fromIndex=othercore],score,..&subq1.q={!term f=child_id
> v=$subq1.row.id}&subq1.rows=3&subq1.sort=price&..
> {code}
> * {{paramPrefix=subq1.}} shifts parameters for subquery: {{subq1.q}} turns to
> {{q}} for subquery, {{subq1.rows}} to {{rows}}
> * {{fromIndex=othercore}} optional param allows to run subquery on other
> core, like it works on query time join
> * the itchiest one is to reference to document field from subquery
> parameters, here I propose to use local param {{v}} and param deference
> {{v=$param}} thus every document field implicitly introduces parameter for
> subquery $\{paramPrefix\}row.$\{fieldName\}, thus above subquery is
> q=child_id:<doc.getField("id")>, presumably we can drop "row." in the middle
> (reducing to v=$subq1.id), until someone deal with {{rows}}, {{sort}} fields.
> * \[subquery\], or \[query\], or ?
> Caveat: it should be a way slow; it handles only search result page, not
> entire result set.
--
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
