Return-Path: Delivered-To: apmail-lucene-general-archive@www.apache.org Received: (qmail 7861 invoked from network); 5 Feb 2010 08:07:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Feb 2010 08:07:13 -0000 Received: (qmail 33728 invoked by uid 500); 5 Feb 2010 08:07:13 -0000 Delivered-To: apmail-lucene-general-archive@lucene.apache.org Received: (qmail 33662 invoked by uid 500); 5 Feb 2010 08:07:12 -0000 Mailing-List: contact general-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@lucene.apache.org Delivered-To: mailing list general@lucene.apache.org Received: (qmail 33651 invoked by uid 99); 5 Feb 2010 08:07:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Feb 2010 08:07:11 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of simon.willnauer@googlemail.com designates 209.85.220.219 as permitted sender) Received: from [209.85.220.219] (HELO mail-fx0-f219.google.com) (209.85.220.219) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Feb 2010 08:07:01 +0000 Received: by fxm19 with SMTP id 19so587927fxm.5 for ; Fri, 05 Feb 2010 00:06:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=UWDhkRZ9aABcnZGvF7SU663vCc75c8ds0BUh3cT2uoM=; b=QUG0zqa05GmqjSdXMEQzU1RAKItmYU096RMlP4gdrZNTHZv9rqVFQJKAsdLOE3vbqg uI01pTKXu+hZvR0jLKgFL7lgR13dG/Po0FFvPkJmuDkUTlL+94dPq9W/DWcmM2xZ6Ujn 4dYbPS6PkwudRoBFMHS45IdmeQkRcnfpMiqyI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; b=GSpQIpUXMhVOlJJHnv5RoRYAZ+Ak0fZ1LCe0WaFxrr1L1LujZv8xEdO4j7FVZhTPOz T0TpsHlVCE6YYhBTq8S38VTnhFNXXJNZ7wn3ZBnQLmHSmdfEalB0wjiHYnqPjCo1AHbw SAseTv2RfSnFoyW2ifRPhSJUAmbXC6e9OmaKo= MIME-Version: 1.0 Received: by 10.239.146.210 with SMTP id x18mr243428hba.77.1265357200392; Fri, 05 Feb 2010 00:06:40 -0800 (PST) Reply-To: simon.willnauer@gmail.com In-Reply-To: <60E5D2D4-ABC7-45AE-8D2C-8E199708D813@apache.org> References: <00e601caa5f8$45ab5810$d1020830$@edu> <60E5D2D4-ABC7-45AE-8D2C-8E199708D813@apache.org> Date: Fri, 5 Feb 2010 09:06:40 +0100 Message-ID: Subject: Re: A Question About Lucene From: Simon Willnauer To: general@lucene.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org On Fri, Feb 5, 2010 at 3:05 AM, Grant Ingersoll wrote: > > On Feb 4, 2010, at 7:15 PM, Mohammed Aziz Parande wrote: > >> Hi, >> >> >> >> I am a graduate student in the Department of Information Systems at the >> University of Maryland, Baltimore County (UMBC). I am doing research in the >> area of software engineering. I would very much appreciate if you could >> answer the following questions of mine: >> >> >> >> 1. I was wondering if Lucene has gone under any major restructuring/redesign >> initiative in its history. Restructuring/redesign initiative can be defined >> as a concerted effort during a time period in which major changes were >> applied to the code base to improve software architecture/design while >> little or no functional enhancement was made. > > Yes it has gone under a restructuring, but it also had other improvements added. > >> >> >> >> 2. If the project has gone under such an initiative, then would it be >> possible for you to give the dates or revision/release numbers that are >> "right before" and "right after" this structuring effort? I would like to >> checkout the source code from the repository to compare structural >> measurements that belong to "before" and "after" snapshots. Note that the >> dates and revision/release numbers should be right before and right after >> the initiative because I would like to be able to isolate and observe the >> effects of this effort. >> > > See the 2.3.X releases, most notably the reworking of indexing. In Lucene 2.9 a lot of changes have been introduced which touched architecture (Analysis API from Token to Attribute, Per-Segment Search) and at the same time changed runtime behaviour. Yet, with 2.9 you can observe how this was introduced with full backwards compatibility for the most parts of lucene. You might find the Lucene 2.9 whitepaper from Lucid Imagination helpful in gives you a rather high level technical overview of what is new in 2.9 (http://www.lucidimagination.com/How-We-Can-Help/whitepaper). For technical details you still have to go into the sources. > > HTH, > Grant