[
https://issues.apache.org/jira/browse/SOLR-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson resolved SOLR-5084.
----------------------------------
Resolution: Fixed
Fix Version/s: 5.0
4.6
I had a bit of work to reconcile the trunk and 4x versions, there's
StorableField used in the patch that's not available in 4.x, but I think it's
just a rename.
We can open up any issues with enums in new JIRAs.
> new field type - EnumField
> --------------------------
>
> Key: SOLR-5084
> URL: https://issues.apache.org/jira/browse/SOLR-5084
> Project: Solr
> Issue Type: New Feature
> Reporter: Elran Dvir
> Assignee: Erick Erickson
> Fix For: 4.6, 5.0
>
> Attachments: Solr-5084.patch, Solr-5084.patch, Solr-5084.patch,
> Solr-5084.patch, Solr-5084.trunk.patch, Solr-5084.trunk.patch,
> Solr-5084.trunk.patch, Solr-5084.trunk.patch, Solr-5084.trunk.patch,
> Solr-5084.trunk.patch, Solr-5084.trunk.patch, Solr-5084.trunk.patch,
> Solr-5084.trunk.patch, enumsConfig.xml, schema_example.xml
>
>
> We have encountered a use case in our system where we have a few fields
> (Severity. Risk etc) with a closed set of values, where the sort order for
> these values is pre-determined but not lexicographic (Critical is higher than
> High). Generically this is very close to how enums work.
> To implement, I have prototyped a new type of field: EnumField where the
> inputs are a closed predefined set of strings in a special configuration
> file (similar to currency.xml).
> The code is based on 4.2.1.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
