[
https://issues.apache.org/jira/browse/SOLR-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Joiner updated SOLR-1986:
--------------------------------
Attachment: AbstractMultiSubTypeFieldType.patch
Since the reason people seemed to object to the patch in the mailing list was
that the AbstractSubTypeFieldType was not originally intended to be used for
multiple different types, I made it a separate class. Also, the subFieldType
parameter now works, and the created subFields are prepended with "subtype_" so
as to allow dynamicFields to be used to simulate multiValued fields.
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
