Return-Path: Delivered-To: apmail-lucene-java-dev-archive@www.apache.org Received: (qmail 97074 invoked from network); 21 May 2009 17:16:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 May 2009 17:16:16 -0000 Received: (qmail 27256 invoked by uid 500); 21 May 2009 17:03:20 -0000 Delivered-To: apmail-lucene-java-dev-archive@lucene.apache.org Received: (qmail 27186 invoked by uid 500); 21 May 2009 17:03:19 -0000 Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@lucene.apache.org Delivered-To: mailing list java-dev@lucene.apache.org Received: (qmail 27136 invoked by uid 99); 21 May 2009 17:03:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 May 2009 17:03:19 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dmsmith555@gmail.com designates 209.85.222.180 as permitted sender) Received: from [209.85.222.180] (HELO mail-pz0-f180.google.com) (209.85.222.180) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 May 2009 17:03:09 +0000 Received: by pzk10 with SMTP id 10so488805pzk.29 for ; Thu, 21 May 2009 10:02:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=i77v+RU9wQnzCzdzMn3YaeORG7wXcF9m863BpL3l8Lk=; b=AwFdEA19Y/U7E08ltk+gxEEOW9amBXlxF86ca332cuSUkTW5MgfJ7+b09sPOtnhV8i 5dY+KzW2FpFQxuL5sLqJt0Dd/AX1A59QEPMHo1OS/27jH48TybdTi08Qr2nwe8L4CGdH nkJExzkJ0+eZ+YO0hlJgh1LnT2hvZkPu2igd0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=QDtdtBV6rHcFfNkwsAfWonCw9QEs5NE9CTNL1RQ2yXhZCmR1G8n7gzeVno3LsulL7E DvCZgRLzNCa30kKSquA7f/rb5qFT//9xQ7HJcfXFmguNyuRzFU+fJldrVlNA8n5QZ99/ SR6/D+hxkt83hs3XgExvCgd7YoSAgDvItTiFU= Received: by 10.142.211.7 with SMTP id j7mr923856wfg.306.1242925367734; Thu, 21 May 2009 10:02:47 -0700 (PDT) Received: from localhost.localdomain (adsl-69-218-243-198.dsl.dytnoh.ameritech.net [69.218.243.198]) by mx.google.com with ESMTPS id 22sm4251457wfi.32.2009.05.21.10.02.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 21 May 2009 10:02:47 -0700 (PDT) Message-ID: <4A158935.6040208@gmail.com> Date: Thu, 21 May 2009 13:02:45 -0400 From: DM Smith User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: java-dev@lucene.apache.org Subject: Re: Lucene's default settings & back compatibility References: <9ac0c6aa0905181406l5c951016k97a16d8db766716e@mail.gmail.com> <9ac0c6aa0905201210l2becda41ic5d51b22fca043e@mail.gmail.com> <786fde50905201224i56c6184et463254a8aeb83949@mail.gmail.com> <9ac0c6aa0905201306p7948fae0sfe57e3a70eebe137@mail.gmail.com> <786fde50905202034n5250bc9dk844c39a7d734668c@mail.gmail.com> <9ac0c6aa0905210417t8b06085j54dd207ac86e76b8@mail.gmail.com> <4EE92A40-F518-4B33-A13D-40CCF521C496@gmail.com> <9ac0c6aa0905210909icaf86c3ke81740e40993adb5@mail.gmail.com> <8f0ad1f30905210919r40dce078uf7f43acecf0b0f91@mail.gmail.com> <9ac0c6aa0905210925q2df382d2v6d8ea95a8cc69c14@mail.gmail.com> In-Reply-To: <9ac0c6aa0905210925q2df382d2v6d8ea95a8cc69c14@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Michael McCandless wrote: > On Thu, May 21, 2009 at 12:19 PM, Robert Muir wrote: > >> even as simple as changing default stopword list for some analyzer could be >> an issue, if the user doesn't re-index in response to that change. >> > > OK, right. > > So say we forgot to include "the" in the default English stopwords > list (yes, an extreme example...). > "The" would be a bug fix. I think most users would expect that to be fixed. They might be willing, as I would be, to require all their indexes using that stopword list to be rebuilt. How about a change that would be a bit more controversial, to which some would agree and others would not. I wonder how many people are creating metadata about indexes so that they can track when an index could/should/must be rebuilt? Some kind of "versioned tool chain info" for the index. If analyzers and filters can change output then it needs to be tracked. -- DM --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org