Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Sun, 24 Apr 2011 23:00:11 +0000 (UTC)
From: "Thomas Joiner (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <2101994934.79202.1303686011152.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (SOLR-1986) Allow users to define multiple
 subfield types in AbstractSubTypeFieldType
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/SOLR-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Joiner updated SOLR-1986:
--------------------------------

    Attachment: SOLR-1986.patch

Finally had a chance to create some tests for it.  I think that the tests that I made cover the functionality of the class fairly well, however if you have any feedback/improvements that you would like me to make, please feel free.

I also improved the documentation for the AbstractMultiSubTypeFieldType class...most of the commenting is probably completely unnecessary for anyone with any familiarity with the Solr core, however to anybody who is trying to create a custom type that isn't familiar with the core, it should help them understand what the class is doing a little bit.

Note that this patch should be applied independently of the original patch

> Allow users to define multiple subfield types in AbstractSubTypeFieldType
> -------------------------------------------------------------------------
>
>                 Key: SOLR-1986
>                 URL: https://issues.apache.org/jira/browse/SOLR-1986
>             Project: Solr
>          Issue Type: Improvement
>          Components: Schema and Analysis
>            Reporter: Mark Allan
>            Priority: Minor
>         Attachments: AbstractMultiSubTypeFieldType.patch, SOLR-1986.patch, multiSubType.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> A few small changes to the AbstractSubTypeFieldType class to allow users to define distinct field types for each subfield.  This enables us to define complex data types in the schema.
> For example, we have our own subclass of the CoordinateFieldType called TemporalCoverage where we store a start and end date for an event but now we can store a name for the event as well.
> <fieldType name="temporal" class="uk.ac.edina.solr.schema.TemporalCoverage" dimension="3" subFieldSuffix="_ti,_ti,_s"/>
> In this example, the start and end dates get stored as trie-coded integer subfields and the description as a string subfield.

--
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