Return-Path: 
 <solr-user-return-41915-apmail-lucene-solr-user-archive=lucene.apache.org@lucene.apache.org>
Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org
Received: (qmail 45697 invoked from network); 6 Oct 2010 13:28:22 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 6 Oct 2010 13:28:22 -0000
Received: (qmail 61904 invoked by uid 500); 6 Oct 2010 13:28:19 -0000
Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org
Received: (qmail 61677 invoked by uid 500); 6 Oct 2010 13:28:17 -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 61668 invoked by uid 99); 6 Oct 2010 13:28:16 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Oct 2010 13:28:16 +0000
X-ASF-Spam-Status: No, hits=3.5 required=10.0
	tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of tommaso.teofili@gmail.com
 designates 209.85.216.176 as permitted sender)
Received: from [209.85.216.176] (HELO mail-qy0-f176.google.com)
 (209.85.216.176)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Oct 2010 13:28:11 +0000
Received: by qyk4 with SMTP id 4so466788qyk.14
        for <solr-user@lucene.apache.org>;
 Wed, 06 Oct 2010 06:27:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:received:in-reply-to
         :references:date:message-id:subject:from:to:content-type;
        bh=R1/tMmnpqPOAO7tOdLK3QoEKMJKGHYTguivgi4A4qkE=;
        b=aCz1UGTzRl8lwwszu9dzgp8jUIOW/e2hHNb5R0Ma/zXxzrqTkTyzhmF99NvJR84+/m
         ImC8J/T8CrTIFSfCZ0fsG92fu7IESb/kePYaJSq1MnTyhaQCUuUSkpYG57goLyJ8euyW
         b81nKJYgTlBHrsS4dUQ02bGKcvX40+K1oLpG0=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=j868zXdBb/LOyXIl/6oKlz+Ns3LdOw9nixAeJsUp6oLWk5V0FjQGRg7N4glnEREKqw
         AEWLFp0ZY2fONvQRf20MaFAqTTl0TCl8D8Do6fluaraeIqZDEp1tYZP6+sxRasU0x6P0
         36mOrPp7UMznP/1ey5fbrOFdM4/oulEA7pVn8=
MIME-Version: 1.0
Received: by 10.224.11.131 with SMTP id t3mr9122862qat.262.1286371670524; Wed,
 06 Oct 2010 06:27:50 -0700 (PDT)
Received: by 10.229.9.69 with HTTP; Wed, 6 Oct 2010 06:27:50 -0700 (PDT)
In-Reply-To: <1286367934634-1642093.post@n3.nabble.com>
References: <AANLkTimqrFPoR-GPDkHCiMwv=51iKFHwZtNfYXe8ZX_8@mail.gmail.com>
	<1285331235611-1573577.post@n3.nabble.com>
	<AANLkTi=ZPyH98dxFUqgWgOCXXbG-kF4=7kv0=rotq7df@mail.gmail.com>
	<1285579913200-1587660.post@n3.nabble.com>
	<AANLkTin9Msv-=MX_VeQ3oJvrXuqx1kL+OwRXmMf37JLj@mail.gmail.com>
	<1285928592064-1613752.post@n3.nabble.com>
	<AANLkTingH=8ZVov1hr7Ln1UCDqCwv4eR9n9g75wae+AN@mail.gmail.com>
	<1286196463247-1629397.post@n3.nabble.com>
	<AANLkTinG=QPM=6-P_qDM29GnBZEi2h+4rD-RyDCbQLPx@mail.gmail.com>
	<1286367934634-1642093.post@n3.nabble.com>
Date: Wed, 6 Oct 2010 15:27:50 +0200
Message-ID: <AANLkTin6Qsqk8Vecoif=1t0TeUbJ3WQArUHZf-+9twqd@mail.gmail.com>
Subject: Re: Solr UIMA integration
From: Tommaso Teofili <tommaso.teofili@gmail.com>
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=000e0cd1f8c87883670491f2be04

--000e0cd1f8c87883670491f2be04
Content-Type: text/plain; charset=ISO-8859-1

Hi Mahesh,
the issue here is that you're not sending a <field name="text">...</field>
to Solr from which UIMAUpdateRequestProcessor extracts text to analyze :)
Infact by default UIMAUpdateRequestProcessor extracts text to analyze from
that field and send that value to a UIMA pipeline.
Obviously you could choose to customize this behavior making
UIMAUpdateRequestProcessor read values from each field that is being indexed
in the document or another field.

However this made me realize that in such situations that field value is a
String "null" and not a null object, as I expected; so line 57 in
UIMAUpdateRequestProcessor should be changed as following to prevent such
errors:
...
if (textFieldValue != null && !"".equals(textFieldValue) &&
!"null".equals(textFieldValue)) {
...
Hope this helps,
Tommaso

2010/10/6 maheshkumar <maheshkumarrp@gmail.com>

>
> Hi Tommaso,
>
> I will try the service call outside Solr/UIMA.
>
> And the text i am using is
>
> FileName: Entity.xml
> <add>
> <doc>
>  <field name="reference">Entity.xml</field>
>  <field name="content">Senator Dick Durbin (D-IL)  Chicago , March 3,
> 2007.</field>
>  <field name="title">Entity Extraction</field>
> </doc>
> </add>
>
> and using curl to index it curl http://localhost:8080/solr/update -F
> solr.body=@Entity.xml
>
> Thanks
> Mahesh
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-UIMA-integration-tp1528253p1642093.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>

--000e0cd1f8c87883670491f2be04--