Return-Path: X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3E31D105A4 for ; Mon, 7 Oct 2013 15:59:04 +0000 (UTC) Received: (qmail 98213 invoked by uid 500); 7 Oct 2013 15:59:02 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 98139 invoked by uid 500); 7 Oct 2013 15:59:02 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 98121 invoked by uid 99); 7 Oct 2013 15:59:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Oct 2013 15:59:00 +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 includes SPF record at spf.trusted-forwarder.org) Received: from [93.93.44.98] (HELO mail.anyware-services.com) (93.93.44.98) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Oct 2013 15:58:56 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.anyware-services.com (Postfix) with ESMTP id B447AA75B for ; Mon, 7 Oct 2013 17:58:34 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at lanfeust.anyware.corp Received: from mail.anyware-services.com ([127.0.0.1]) by localhost (lanfeust.anyware [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gs7IisehbuwW for ; Mon, 7 Oct 2013 17:58:34 +0200 (CEST) Received: from [172.31.2.33] (maya.anyware.corp [172.31.2.33]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.anyware-services.com (Postfix) with ESMTPSA id 5F1AD9FE2 for ; Mon, 7 Oct 2013 17:58:34 +0200 (CEST) Message-ID: <5252DA2A.1000207@apache.org> Date: Mon, 07 Oct 2013 17:58:34 +0200 From: =?ISO-8859-1?Q?C=E9dric_Damioli?= Organization: Apache Softwarae Foundation User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: dev@jackrabbit.apache.org Subject: Upgrade to Lucene 4 ? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, I'm thinking about the potential migration of Jackrabbit to Lucene 4. This represents quite a huge work, as many Lucene core API have completely changed between 3.x and 4.x A quick test by replacing Lucene 3.x by Lucene 4.x shows almost 1000 compilation problems. So before beginning this, I was first wondering if it is even worth doing it. The main benefits are obviously Lucene 4 new features and performance optimizations. The main drawback is IMHO that for a given application, a Jackrabbit migration would also involve the migration of all Lucene-related code if any. Existing repositories should also be reindexed during migration. So what do people think about this ? And of course, if it seems a good idea, is there some committers around here volunteering to help me to do the job ? ;) Best regards, -- C�dric Damioli CMS - Java - Open Source www.ametys.org