Return-Path: Delivered-To: apmail-uima-user-archive@www.apache.org Received: (qmail 64704 invoked from network); 13 Apr 2011 12:45:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 13 Apr 2011 12:45:29 -0000 Received: (qmail 25899 invoked by uid 500); 13 Apr 2011 12:45:29 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 25865 invoked by uid 500); 13 Apr 2011 12:45:29 -0000 Mailing-List: contact user-help@uima.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@uima.apache.org Delivered-To: mailing list user@uima.apache.org Received: (qmail 25857 invoked by uid 99); 13 Apr 2011 12:45:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Apr 2011 12:45:29 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [141.35.1.28] (HELO fsuj26.rz.uni-jena.de) (141.35.1.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Apr 2011 12:45:22 +0000 Received: from mailsmtp2.rz.uni-jena.de (mailsmtp2.rz.uni-jena.de [141.35.1.21]) by fsuj26.rz.uni-jena.de (8.13.8/8.13.8) with ESMTP id p3DCixPe007360 for ; Wed, 13 Apr 2011 14:44:59 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uni-jena.de; s=dkim-2011; t=1302698699; bh=5aMszudhTOQoCpTLBD6+yivPC76u3Wzxy3i7PAYphP8=; h=Message-ID:Date:From:To:Subject; b=A0y8BbprFw0cwUcCVLOUUkTxQtGxYmYGsTHnVvL8SWx0EqPk2wEa/45usTVqf6OhD m/5nI/T+WXYJcj3GNOYK4Oi0X+L6gahhkvlCscHCyJnTHAROuCX3jrQwJi29xQl4EV MjDHxkdHArVH+UXxu9hc/cvEH3n0himaPiJDoKww= Received: from [141.35.141.140] (autokino.coling.uni-jena.de [141.35.141.140]) (authenticated id=erik.faessler@uni-jena.de bits=0) by mailsmtp2.rz.uni-jena.de (8.13.1/8.13.1) with ESMTP id p3DCixoG016689 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 13 Apr 2011 14:44:59 +0200 Message-ID: <4DA59ACB.6080409@uni-jena.de> Date: Wed, 13 Apr 2011 14:44:59 +0200 From: =?ISO-8859-1?Q?Erik_F=E4=DFler?= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.9) Gecko/20100914 SUSE/3.1.4 Thunderbird/3.1.4 MIME-Version: 1.0 To: user@uima.apache.org Subject: Re: Sandbox: LuCas Lucene update References: <4DA5904F.7060305@uni-jena.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hello Tommaso, thanks a lot for your reply :) I will follow the steps you gave me as soon as there is a little time for this. Also thanks for the SolrCas hint. I think we already talked about this. As far as I understood, Solrcas as well as the Solr-UIMA integration lack some of the features offered by LuCas, for example the alignment of TokenStreams which allows you to merge multiple CAS indexes into a single Lucene field where position_increments are adjusted to stack Lucene tokens with the same offsets. Please (!!) tell me when I'm wrong here, as I am still working on my own ways to use UIMA together with Solr. Thanks again and warm regards, Erik Am 13.04.2011 14:16, schrieb Tommaso Teofili: > Hello Erik, > that would be a very valuable contribution indeed! > > The common way of contributing code is creating a patch file which contains > the differences between your current working copy and the latest revision > available in SVN; you can check better how to do this at > http://www.apache.org/dev/contributors.html#patches . > Then you create a Jira issue under the UIMA project [1] and attach the > created file to the issue. > At that point a committer will review your patch and will commit it if > everything is fine :) > > As a side note if you want to use Solr within a UIMA pipeline you could be > interested in Solrcas [2] or in the Solr-UIMA integration available in Solr > 3.1.0 release [3]. > > Hope this helps, > Tommaso > > [1] : https://issues.apache.org/jira/browse/UIMA > [2] : http://uima.apache.org/sandbox.html#solrcas.consumer > [3] : http://wiki.apache.org/solr/SolrUIMA > > 2011/4/13 Erik F��ler > >> Hey all, >> >> back in January, I had the need to have the CAS Lucene indexer (LuCas, UIMA >> Sandbox component) working with Lucene 2.9.x. So I checked it out from the >> Sandbox SVN, updated the libraries and fixed the compiling bugs. The result >> is a LuCas component working with Lucene 2.9.3. At least all tests are >> working and I used the component (together with Solr which was why I needed >> Lucene 2.9.x) successfully. >> The changes needed were not too big as I did not take the leap to Lucene >> 3.x. Some filters have been updated to the new Token API and one or two >> classes required a more or less complete rewrite until the tests would work >> again. >> >> So, my question: Would it be desirable to commit these changes back to the >> Sandbox SVN? Which steps would have I have to take for this? Or should I >> just send my sources to a developer? The component has been created in my >> lab originally, but the developer has moved to another working place quite a >> while ago. >> >> Best regards, >> >> Erik >>