You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/03/14 13:12: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=16792630#comment-16792630 ] 

ASF subversion and git services commented on SOLR-13129:
--------------------------------------------------------

Commit c2a6772f1edd506c114a4e8179bd09e928f97b49 in lucene-solr's branch refs/heads/master from Moshe
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=c2a6772 ]

SOLR-13129: nested docs: add more/better documentation in Solr ref-guide


> 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: 12h 20m
>  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