From dev-return-321763-archive-asf-public=cust-asf.ponee.io@lucene.apache.org Wed May 9 23:53:09 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 9A750180649 for ; Wed, 9 May 2018 23:53:08 +0200 (CEST) Received: (qmail 96423 invoked by uid 500); 9 May 2018 21:53:02 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 96408 invoked by uid 99); 9 May 2018 21:53:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 May 2018 21:53:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 4F2A51807BC for ; Wed, 9 May 2018 21:53:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id JZx_ugUnpjGy for ; Wed, 9 May 2018 21:53:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id DB1785F1B4 for ; Wed, 9 May 2018 21:53:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 5EFB9E12B6 for ; Wed, 9 May 2018 21:53:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1BE6021298 for ; Wed, 9 May 2018 21:53:00 +0000 (UTC) Date: Wed, 9 May 2018 21:53:00 +0000 (UTC) From: "Hoss Man (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SOLR-12298) Index Full nested document Hierarchy For Queries (umbrella issue) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SOLR-12298?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1646= 9560#comment-16469560 ]=20 Hoss Man commented on SOLR-12298: --------------------------------- bq. Quoting Hoss Man here inline (hoping for his input): I don't have a lot of input / opinions on this general topic of childDocs a= t the moment... From skimming the issue description & last few comments I gather the push h= ere is to make the "arbitrary nested documents of different types" experien= ce/API for *external clients* simpler/easier/cleaner/sexier ... and to then= have rules/conventions enforced by Solr (either via URPs or the underlying= DUH, ... not certain which exactly is being suggested at the moment) handl= e the mapping of those "external relationships" into the *internal* nested = childDocs w/new fields based on the original hierarchy. Ie: an external client could psueod-code documents that look like via {{pa= rentDoc[ ...normalfields..., someFieldName =3D> childDoc1[...], someOtherFi= eldName =3D> childDoc2[...] ]}} and then something in solr would translate = that into the _internal_ representation of nested documents by moving that= relationship info into fields of the child documents ala... {{parentDoc[ .= ..normalfields..., \_childDocuments\_=3D>[ childDoc1[ ..., typeField =3D> s= omeFieldName], childDoc2[ ..., typeField =3D> someOtherFieldName]]}} . (An= d i guess, also add some ohter standard metadata fields to every doc like w= hat the type of the ancestors are?) Or to put it another way: give solr the power to do _internally_ what clien= ts currently have to do _externally_ to model this information. is that about right? This approach seems fine in general ... off the top of my head the biggest = concern i can think of is how how you make something like the JSON ContentL= oader smart enough to tell the differnece between a "child document express= ed as JSON object/map (in a field)" from "atomic update (of a field) as a J= SON object/map" (not an issue with the XML ContentLoader since the {{= }} tag is distinct from the {{}} FWIW: i don't particularly remember making those ~6year old comments/questi= ons fromSOLR-3535 cited here, but i'm guessing my concerns at the time wher= e just that these questions all needed answered in order to take that leap,= and that until/unless we had those answers it seemed simplest to move forw= ard with exposing a "lower level" modeling of child documents so users coul= d take advantage of it ... if we're ready to answer those questions to supp= ort a cleaner/simpler API then by all means let's support it) > Index Full nested document Hierarchy For Queries (umbrella issue) > ----------------------------------------------------------------- > > Key: SOLR-12298 > URL: https://issues.apache.org/jira/browse/SOLR-12298 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public)=20 > Reporter: mosh > Priority: Major > > Solr ought to have the ability to index deeply nested objects, while stor= ing the original document hierarchy. > Currently the client has to index the child document's full path and lev= el to manually reconstruct the original document structure, since the child= ren are flattened and returned in the reserved "__childDocuments__" key. > Ideally you could index a nested document, having Solr transparently add = the required fields while providing a document transformer to rebuild the o= riginal document's hierarchy. > =C2=A0 > This issue is an umbrella issue for the particular tasks that will make i= t all happen =E2=80=93 either subtasks or issue linking. -- 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