Return-Path: Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: (qmail 39940 invoked from network); 11 Mar 2011 03:36:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 11 Mar 2011 03:36:09 -0000 Received: (qmail 50221 invoked by uid 500); 11 Mar 2011 03:36:08 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 50171 invoked by uid 500); 11 Mar 2011 03:36:07 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 50164 invoked by uid 99); 11 Mar 2011 03:36:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Mar 2011 03:36:07 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gento0nz@gmail.com designates 209.85.210.176 as permitted sender) Received: from [209.85.210.176] (HELO mail-iy0-f176.google.com) (209.85.210.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Mar 2011 03:36:02 +0000 Received: by iyj12 with SMTP id 12so3479144iyj.35 for ; Thu, 10 Mar 2011 19:35:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=1DmwBNCKzmVnrzBZNiOY7+Oew1rniwv9HiVA4YN0L/M=; b=FdilJHXPKqi0/99Tqn61LfmqOnqxffUw9Z0KGjxLdph+5h/2y1JhnJyMW5r43lK1ZQ CZO2tpxBFuLi0faFy4DLQld3iSLiYysmc/LuPI+XYva9m19FvYaf1aavcMqZ3yOT6L8l a4AqQ83ELFVRFD3v7sriRiGtPgvReFFi90ZIo= 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; b=hzhGFz1+ZqwsBM3AwxTYpBBwXX75mmKR+FR8bJqCBm8Hqnhfrn3gNUaaVaormgtSzd i0LAigo73XB4eBnwwpOPFy1jQIl4V6YUpWCUg1AIVSGl7wmUe3TffHEKBJi3oNmfBolG 4EFiUjm28yZgtJZLXZqp/jlrL6jjlxaIfAud0= MIME-Version: 1.0 Received: by 10.231.36.11 with SMTP id r11mr6328823ibd.179.1299814541074; Thu, 10 Mar 2011 19:35:41 -0800 (PST) Received: by 10.231.30.77 with HTTP; Thu, 10 Mar 2011 19:35:41 -0800 (PST) In-Reply-To: <393549528.11456.1299781559473.JavaMail.tomcat@hel.zones.apache.org> References: <393549528.11456.1299781559473.JavaMail.tomcat@hel.zones.apache.org> Date: Fri, 11 Mar 2011 16:35:41 +1300 Message-ID: Subject: Re: [jira] Updated: (LUCENE-2308) Separately specify a field's type From: Chris Male To: dev@lucene.apache.org Content-Type: multipart/alternative; boundary=000325550e5afea251049e2ca7f6 --000325550e5afea251049e2ca7f6 Content-Type: text/plain; charset=ISO-8859-1 I'm still likely to take a shot at this myself, assuming someone from GSOC doesn't whip up something first. On Fri, Mar 11, 2011 at 7:25 AM, Michael McCandless (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/LUCENE-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] > > Michael McCandless updated LUCENE-2308: > --------------------------------------- > > Labels: gsoc2011 lucene-gsoc-11 (was: ) > > > Separately specify a field's type > > --------------------------------- > > > > Key: LUCENE-2308 > > URL: https://issues.apache.org/jira/browse/LUCENE-2308 > > Project: Lucene - Java > > Issue Type: Improvement > > Components: Index > > Reporter: Michael McCandless > > Labels: gsoc2011, lucene-gsoc-11 > > Fix For: 4.0 > > > > > > This came up from dicussions on IRC. I'm summarizing here... > > Today when you make a Field to add to a document you can set things > > index or not, stored or not, analyzed or not, details like omitTfAP, > > omitNorms, index term vectors (separately controlling > > offsets/positions), etc. > > I think we should factor these out into a new class (FieldType?). > > Then you could re-use this FieldType instance across multiple fields. > > The Field instance would still hold the actual value. > > We could then do per-field analyzers by adding a setAnalyzer on the > > FieldType, instead of the separate PerFieldAnalzyerWrapper (likewise > > for per-field codecs (with flex), where we now have > > PerFieldCodecWrapper). > > This would NOT be a schema! It's just refactoring what we already > > specify today. EG it's not serialized into the index. > > This has been discussed before, and I know Michael Busch opened a more > > ambitious (I think?) issue. I think this is a good first baby step. We > could > > consider a hierarchy of FIeldType (NumericFieldType, etc.) but maybe hold > > off on that for starters... > > -- > This message is automatically generated by JIRA. > For more information on JIRA, see: http://www.atlassian.com/software/jira > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org > For additional commands, e-mail: dev-help@lucene.apache.org > > -- Chris Male | Software Developer | JTeam BV.| www.jteam.nl --000325550e5afea251049e2ca7f6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I'm still likely to take a shot at this myself, assuming someone f= rom GSOC doesn't whip up something first.

On Fri, Mar 11, 2011 at 7:25 AM, Michael McCandless = (JIRA) <jira@apache= .org> wrote:

=A0 =A0 [ https://issues.apache.org/jira/browse/LUCENE-2308?page=3Dcom.atlas= sian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael McCandless updated LUCENE-2308:
---------------------------------------

=A0 =A0Labels: gsoc2011 lucene-gsoc-11 =A0(was: )

> Separately specify a field's type
> ---------------------------------
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Key: LUCENE-2308
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 URL: https://issues.apache.org/ji= ra/browse/LUCENE-2308
> =A0 =A0 =A0 =A0 =A0 =A0 Project: Lucene - Java
> =A0 =A0 =A0 =A0 =A0Issue Type: Improvement
> =A0 =A0 =A0 =A0 =A0Components: Index
> =A0 =A0 =A0 =A0 =A0 =A0Reporter: Michael McCandless
> =A0 =A0 =A0 =A0 =A0 =A0 =A0Labels: gsoc2011, lucene-gsoc-11
> =A0 =A0 =A0 =A0 =A0 =A0 Fix For: 4.0
>
>
> This came up from dicussions on IRC. =A0I'm summarizing here... > Today when you make a Field to add to a document you can set things > index or not, stored or not, analyzed or not, details like omitTfAP, > omitNorms, index term vectors (separately controlling
> offsets/positions), etc.
> I think we should factor these out into a new class (FieldType?).
> Then you could re-use this FieldType instance across multiple fields.<= br> > The Field instance would still hold the actual value.
> We could then do per-field analyzers by adding a setAnalyzer on the > FieldType, instead of the separate PerFieldAnalzyerWrapper (likewise > for per-field codecs (with flex), where we now have
> PerFieldCodecWrapper).
> This would NOT be a schema! =A0It's just refactoring what we alrea= dy
> specify today. =A0EG it's not serialized into the index.
> This has been discussed before, and I know Michael Busch opened a more=
> ambitious (I think?) issue. =A0I think this is a good first baby step.= =A0We could
> consider a hierarchy of FIeldType (NumericFieldType, etc.) but maybe h= old
> off on that for starters...

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

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




--
Chris Male | Sof= tware Developer | JTeam BV.| www.jteam.nl
--000325550e5afea251049e2ca7f6--