lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Commented] (SOLR-5084) new field type - EnumField
Date Fri, 09 Aug 2013 00:25:49 GMT


Hoss Man commented on SOLR-5084:

bq. If you want to rename a label, thats fine, but you cant really change the sort order without

No, no .. of course not ... i wasn't suggestiong you could change the order, just:
* *remove* a legal value from the list (w/o causing hte validation to complain)
* add new values to the end of the list
* (as you mentioned) modify the label on an existing value

See the example i posted before about removing "Medium" but keeping "High" & "Critical"
exactly as they are -- no change in indexed data, just a way to tell the validation logic
you were talking about adding "skip this value, i removed it on purpose" (or i suppose: "skip
this value, i'm reserving it as a placeholder for future use")
> new field type - EnumField
> --------------------------
>                 Key: SOLR-5084
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Elran Dvir
>         Attachments: enumsConfig.xml, schema_example.xml, Solr-5084.patch, Solr-5084.patch
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message