[
https://issues.apache.org/jira/browse/SOLR-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008449#comment-13008449
]
Thomas Joiner commented on SOLR-1986:
-------------------------------------
I don't currently have a test for it, however I will see about making one (it
may take a while as work has me quite busy right now).
> 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, 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
