[
https://issues.apache.org/jira/browse/SOLR-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated SOLR-5084:
---------------------------------
Attachment: Solr-5084.trunk.patch
Some changes/additions. Mostly this is making tests work. The addition of the
enum to the schema.xml file caused failures in other places that used that file
but didn't have access to the underlying config files. I suspect they were
somehow being found on Elran's machine but not on mine.
Anyway, new patch. I'll be committing momentarily.
> 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
> 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,
> 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]
