Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of billnbell@gmail.com designates
 209.85.161.48 as permitted sender)
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:content-transfer-encoding;
        b=bBBIKPPu+5LpguoamazQfdS6dHb/FOJf3U8LOSMPxgMVQUZzaeaP6DlB7uaIKYV+Di
         2MvTDJ36aP/4uvTnYhdU6qHDPtk1LWIse3BKspxuV34GTZG9AG5ssY0yJttTy9X40rI2
         EYEyRetBHlsYHh2nVJYsnr8DU4+6UUeUEjJeQ=
MIME-Version: 1.0
In-Reply-To: <AANLkTikBCiYCvWv2O4uhYLox=J_u=Qjdn1tCP9G7Ptu6@mail.gmail.com>
References: <4893A353-9F9B-4780-9844-2011E71C9B0E@cominvent.com>
	<AANLkTimCkbO+az_kwtcKciES=kD=huD4Josq63zXnk9g@mail.gmail.com>
	<D8FDBE3A-4220-4B9E-9C26-C0B838E7777C@cominvent.com>
	<AANLkTi=PEr00rMxqxpGqNgC3OrfHucfUkv9HQwvOJQoF@mail.gmail.com>
	<1F82A5CC-45FA-4D25-919E-E81A00152A60@cominvent.com>
	<17E629B6-442F-4E26-B3EA-C574A5AB474B@cominvent.com>
	<AANLkTikBCiYCvWv2O4uhYLox=J_u=Qjdn1tCP9G7Ptu6@mail.gmail.com>
Date: Sun, 27 Feb 2011 21:23:03 -0700
Message-ID: <AANLkTinCvnhVfmvMYa187Qx1Uoj=FNp-sd8x38630tHw@mail.gmail.com>
Subject: Re: Example schema - fieldType phonetic
From: William Bell <billnbell@gmail.com>
To: dev@lucene.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

SOLR-2393

Hopefully I cut and pasted properly.


On Fri, Feb 25, 2011 at 7:14 AM, Ryan McKinley <ryantxu@gmail.com> wrote:
> Ya, I suppose the PhoneticFilterFactory could check
> "DoubleMetaphone".equals( encoder ) and then create the specialized
> Filter.
>
> I don't feel strongly, but we could have:
> EncoderFilter -- just uses 'encode()'
> DoubleMetaphoneFilter - uses special double metaphone stuff
>
> EncoderFilterFactory -- always uses EncoderFilter, and is not
> semantically bound to 'phonetic'
> PhoneticFilterFactory -- picks the best phonetic filter impl (encoder
> or double metaphone)
>
> then deprecate:
> PhoneticFilter
> DoubleMetaphoneFilterFactory
>
> Does that make sense? =C2=A0If so, lets make a JIRA issue for it
>
> ryan
>
>
> On Fri, Feb 25, 2011 at 4:43 AM, Jan H=C3=B8ydahl <jan.asf@cominvent.com>=
 wrote:
>> Technically it would be possible for the PhoneticFilterFactory to return=
 a DoubleMetaphoneFilter for that specific case. Otherwise it would be bett=
er to just remove support for DoubleMetaphone from the PhoneticFilterFactor=
y and refer to the specialized factory?
>>
>> --
>> Jan H=C3=B8ydahl, search solution architect
>> Cominvent AS - www.cominvent.com
>>
>> On 25. feb. 2011, at 10.07, Jan H=C3=B8ydahl wrote:
>>
>>> Then it's funny that only the PhoneticFilter is mentioned on the WIKI w=
hile the DoubleMetaphone is not?
>>>
>>> What would be the correct way to resolve this mismatch aside from fixin=
g the documentation?
>>>
>>> --
>>> Jan H=C3=B8ydahl, search solution architect
>>> Cominvent AS - www.cominvent.com
>>>
>>> On 24. feb. 2011, at 18.10, Ryan McKinley wrote:
>>>
>>>>>
>>>>> Is this difference on purpose?
>>>>
>>>> If I were to do it again... 'PhoneticFilter' should really be
>>>> EncoderFilter since it just uses the encoder API to generate tokens.
>>>> There is nothing specific to 'phonetic' -- In fact, when I implement
>>>> KStem, I use the PhoneticFilter?!
>>>> https://issues.apache.org/jira/browse/SOLR-379?focusedCommentId=3D1293=
4562&page=3Dcom.atlassian.jira.plugin.system.issuetabpanels:comment-tabpane=
l#comment-12934562
>>>>
>>>> DoubleMetaphone however uses the DoubleMetaphone API and generatates
>>>> special tokens based on that.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org