You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2019/02/04 05:36:00 UTC
[jira] [Commented] (SOLR-13129) Document nested child docs in the
ref guide
[ https://issues.apache.org/jira/browse/SOLR-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759645#comment-16759645 ]
David Smiley commented on SOLR-13129:
-------------------------------------
It's getting close to finished now. [~ctargett] could you please take a look at the PR? Of course anyone's input here is welcome. I'm particularly interested in your opinion on the placement in the TOC. Moshe has placed it at a top level _following_ Searching Documents. I suppose I like it there but it's debatable -- the top level is after all more important than other levels. If this were to move to somewhere else, I could imagine it _underneath_ Searching.
On the other hand... I could also imagine a point of view in which it's split into two -- a schema part and a searching part. There are multiple ways to slice it I guess. Hopefully others appreciate the one-stop shopping for info about nested documents.
> 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
>
> Time Spent: 5h
> Remaining Estimate: 0h
>
> 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