Return-Path: 
 <solr-user-return-70914-apmail-lucene-solr-user-archive=lucene.apache.org@lucene.apache.org>
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 CEC7BD553
	for <apmail-lucene-solr-user-archive@minotaur.apache.org>;
 Fri, 24 Aug 2012 15:31:56 +0000 (UTC)
Received: (qmail 25420 invoked by uid 500); 24 Aug 2012 15:31:53 -0000
Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org
Received: (qmail 25382 invoked by uid 500); 24 Aug 2012 15:31:53 -0000
Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:solr-user-help@lucene.apache.org>
List-Unsubscribe: <mailto:solr-user-unsubscribe@lucene.apache.org>
List-Post: <mailto:solr-user@lucene.apache.org>
List-Id: <solr-user.lucene.apache.org>
Reply-To: solr-user@lucene.apache.org
Delivered-To: mailing list solr-user@lucene.apache.org
Received: (qmail 25373 invoked by uid 99); 24 Aug 2012 15:31:53 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Aug 2012 15:31:53 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy)
Received: from [78.47.156.132] (HELO mail.cms-agenten.de) (78.47.156.132)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Aug 2012 15:31:44 +0000
Received: by mail.cms-agenten.de (Postfix, from userid 5001)
	id 0713025147; Fri, 24 Aug 2012 17:31:24 +0200 (CEST)
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on vhs1.cms-agenten.de
X-Spam-Level: 
Received: from galvano.fritz.box (host-188-174-194-182.customer.m-online.net
 [188.174.194.182])
	by mail.cms-agenten.de (Postfix) with ESMTPSA id 79A0724FCA
	for <solr-user@lucene.apache.org>; Fri, 24 Aug 2012 17:31:18 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: Re: Debugging DIH
From: Chantal Ackermann <c.ackermann@it-agenten.com>
In-Reply-To: <C1961114-ED3F-4EC6-82B8-49B8B2981856@petdance.com>
Date: Fri, 24 Aug 2012 17:31:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <31746D4D-0F57-4651-AB33-19188BD1D394@it-agenten.com>
References: 
 <CAP+bYWAG21aUzpZf7zwJPyRHowmW=42cmGT1Bwwb-=OB_OKftw@mail.gmail.com>
 <C1961114-ED3F-4EC6-82B8-49B8B2981856@petdance.com>
To: solr-user@lucene.apache.org
X-Mailer: Apple Mail (2.1278)
X-Old-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00,
	FSL_RCVD_USER autolearn=ham version=3.3.1

>=20
> I don't see that you have anything in the DIH that tells what columns =
from the query go into which fields in the index.  You need something =
like
>=20
> <field name=3D"location" column=3D"location" />
> <field name=3D"amount" column=3D"amount" />
> <field name=3D"when" column=3D"when" />
>=20

That is not completely true. If the columns have the same names as the =
fields, the mapping is redundant. Nevertheless, it might be the problem. =
What I've experienced with Oracle, at least, is that the columns would =
be returned in uppercase even if my alias would be in lowercase. You =
might force it by adding quotes, though. Or try adding

<field name=3D"location" column=3D"LOCATION" />
<field name=3D"amount" column=3D"AMOUNT" />
<field name=3D"when" column=3D"WHEN" />

You might check in your preferred SQL client how the column names are =
returned. It might be an indicator. (At least, in my case they would be =
uppercase in SQL Developer.)

Cheers,
Chantal=