From solr-user-return-145291-archive-asf-public=cust-asf.ponee.io@lucene.apache.org Wed Dec 5 12:27:58 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 8FBA518062B for ; Wed, 5 Dec 2018 12:27:57 +0100 (CET) Received: (qmail 72091 invoked by uid 500); 5 Dec 2018 11:27:55 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Delivered-To: moderator for solr-user@lucene.apache.org Received: (qmail 61165 invoked by uid 99); 5 Dec 2018 10:33:30 -0000 X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.31 X-Spam-Level: ** X-Spam-Status: No, score=2.31 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_LOW=-0.7, T_REMOTE_IMAGE=0.01] autolearn=disabled X-Originating-IP: 88.172.8.152 From: "Bruno Mannina" To: Subject: Nested Documents without using "type" field ? Possible or Not ? Date: Wed, 5 Dec 2018 11:33:18 +0100 Message-ID: <025c01d48c85$f07c8b60$d175a220$@com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_025D_01D48C8E.5240F360" X-Mailer: Microsoft Office Outlook 12.0 Content-Language: fr Thread-Index: AdSMhfAR7Chr2P0rRV6fTLwugQjvlQ== X-Antivirus: Avast (VPS 181204-4, 04/12/2018), Outbound message X-Antivirus-Status: Clean ------=_NextPart_000_025D_01D48C8E.5240F360 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, I would like to use SOLR to index the Cooperative Patent Classification, The CPC has a hierarchical structure and it can have more than 20 level. It's a basic structure without Type of nested doc. i.e: A -> A01 -> A01B -> A01B3/00 -> A01B3/40 -> A01B3/4025 . A -> A01 -> A01L -> A01L1/00 -> A01L1/012 -> A01L1/0125 . B -> B05 -> B05C -> B05C10/00 -> B05C10/87 Important: Each "Code" has a Definition (free text used to explain the code). A record is: Code + Definition - I already indexed this CPC structure with a XML format it works fine. - With this kind of structure I can't set a type of nested doc. - A keyword that a user search can be found in several levels (parent and child) So, my tests: If I set a field named "typedoc" with "parentDoc" or "leaf", I'm facing an error when I used ParentFilter, ChildFilter, etc. "Child query must only match non-parent docs" q=3D{!parent which=3D"typedoc:parentDoc"}ti:details fq=3D*,[child parentFilter=3D"typedoc:parentDoc" childFilter=3D"ti:details"= ] I need to have the whole structure when I do a query. I mean, I need to hav= e all parents until level=3D1 My question is: Is someone have already indexed and used this kind of structure ? All information I found use typedoc field. Thanks for your help ! Cordialement, Best Regards Bruno --- L'absence de virus dans ce courrier =C3=A9lectronique a =C3=A9t=C3=A9 v=C3= =A9rifi=C3=A9e par le logiciel antivirus Avast. https://www.avast.com/antivirus ------=_NextPart_000_025D_01D48C8E.5240F360--