You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Allan (JIRA)" <ji...@apache.org> on 2010/07/05 13:27:50 UTC
[jira] Updated: (SOLR-1986) Allow users to define multiple subfield
types in AbstractSubTypeFieldType
[ https://issues.apache.org/jira/browse/SOLR-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Allan updated SOLR-1986:
-----------------------------
Attachment: multiSubType.patch
Patch to provide initial functionality of multiple subfield types.
> 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: 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org