Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CAEE410A0D for ; Tue, 14 Jan 2014 19:02:25 +0000 (UTC) Received: (qmail 78052 invoked by uid 500); 14 Jan 2014 18:59:15 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 77075 invoked by uid 500); 14 Jan 2014 18:57:48 -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 Received: (qmail 69980 invoked by uid 99); 14 Jan 2014 18:52:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jan 2014 18:52:32 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bill.w.au@gmail.com designates 209.85.212.170 as permitted sender) Received: from [209.85.212.170] (HELO mail-wi0-f170.google.com) (209.85.212.170) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jan 2014 18:52:25 +0000 Received: by mail-wi0-f170.google.com with SMTP id hq4so4842182wib.3 for ; Tue, 14 Jan 2014 10:52:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=k7kgG8TpaeK0FqcJ5147A1iQfYuzr5Kr7pjZRJFlC9w=; b=eyM3t2DMhR206QaWA4i4EO9Jb5w5zRKZvNj3k1HoyKRPg2uUB9aeYb6FWiB4jKZAXu BiqI5fmFrjs6lZvvjyp1o4NJ1xa21AVBlsZxrhcyzprgEpVnIPs3a6/VzeONxmo/pEUN u/HkS4LtfPA6H+nnN5ngBKnNrYgyYzbMvM3BKz6T5fqUXjSvpsv+b878Hducr8SNDSab mGFuHcihvaTk6nP/TtWtxSwlZNZrJSy5hwMrx1WBBLvcBcnNS7MPasZmDtTQVWk21saq iKFqPyGIrtn8CVPWyu11ju56QBRhwTPIMKrBiiT0U9J/IwvfjdN2KFw4+o8fCZNHvwf9 dnPg== MIME-Version: 1.0 X-Received: by 10.180.211.101 with SMTP id nb5mr730470wic.0.1389725525328; Tue, 14 Jan 2014 10:52:05 -0800 (PST) Received: by 10.180.93.200 with HTTP; Tue, 14 Jan 2014 10:52:05 -0800 (PST) In-Reply-To: <52D48CEB.1080809@elyograg.org> References: <52D48CEB.1080809@elyograg.org> Date: Tue, 14 Jan 2014 13:52:05 -0500 Message-ID: Subject: Re: question about DIH solr-data-config.xml and XML include From: Bill Au To: "solr-user@lucene.apache.org" Content-Type: multipart/alternative; boundary=001a11c37cc645c66204eff2b068 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c37cc645c66204eff2b068 Content-Type: text/plain; charset=ISO-8859-1 The problem is with the admin UI not following the XML include to find entity so it found none. DIH itself does support XML include as I can issue the DIH commands via HTTP on the included entities successfully. Bill On Mon, Jan 13, 2014 at 8:03 PM, Shawn Heisey wrote: > On 1/13/2014 3:31 PM, Bill Au wrote: > >> But when I use XML include, the Entity pull-down in the Dataimport section >> of the Solr admin UI is empty. I know that happens when there is a syntax >> error in solr-data-config.xml. Does DIH supports XML include? Also I am >> not seeing any error message in the log even if I set log level to ALL. >> Is >> there any way to get DIH to log what it thinks is wrong >> solr-data-cofig.xml? >> > > Paying it forward. Someone on this mailing list helped me with this. I > have tested this DIH configand found that it works: > > > > driver="com.mysql.jdbc.Driver" > encoding="UTF-8" > url="jdbc:mysql://${dih.request.dbHost}:3306/${dih.request.dbSchema}? > zeroDateTimeBehavior=convertToNull" > batchSize="-1" > user="REDACTED" > password="REDACTED"/> > > > > > > The xlmns:xi attribute in the outer tag makes it possible to use the > xi:include syntax later. > > I make extensive use of this in my solrconfig.xml file. There's almost no > actual config in that file, everything is included from other files. > > When you look at the config in the admin UI, you will not see the included > text, you'll only see the xi:include tag. > > Thanks, > Shawn > > --001a11c37cc645c66204eff2b068--