lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mosh (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-13129) Document nested child docs in the ref guide
Date Thu, 17 Jan 2019 11:59:00 GMT

    [ https://issues.apache.org/jira/browse/SOLR-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744960#comment-16744960
] 

mosh edited comment on SOLR-13129 at 1/17/19 11:58 AM:
-------------------------------------------------------

 

this is a more complex issue that has multiple aspects – more "cross-cutting", and so IMO
doesn't belong in the current doc pigeon holes.\{quote}
 I have been wondering whether this topic deserves its own page in the ref guide.
 WDYT?

 


was (Author: moshebla):
{quote}this is a more complex issue that has multiple aspects – more "cross-cutting", and
so IMO doesn't belong in the current doc pigeon holes.\{quote}
I am wondering whether this topic deserves its own page in the ref guide.
WDYT?

> Document nested child docs in the ref guide
> -------------------------------------------
>
>                 Key: SOLR-13129
>                 URL: https://issues.apache.org/jira/browse/SOLR-13129
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation
>    Affects Versions: 8.0
>            Reporter: David Smiley
>            Priority: Major
>             Fix For: 8.0
>
>
> Solr 8.0 will have nicer support for nested child documents than its predecessors.  This
should be documented in one place in the ref guide (to the extent that makes sense). Users
need to the schema ramifications (incl. special fields and that some aspects are optional
and when), what a nested document "looks like" (XML, JSON, SolrJ), how to use the child doc
transformer, how to use block join queries, and get some overview of how this all works.  Maybe
mention some plausible future enhancements / direction this is going in (e.g. path query language?).
 Some of this is already done but it's in various places and could be moved.  Unlike other
features which conveniently fit into one spot in the documentation (like a query parser),
this is a more complex issue that has multiple aspects – more "cross-cutting", and so IMO
doesn't belong in the current doc pigeon holes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message