lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson (JIRA)" <>
Subject [jira] [Commented] (SOLR-5084) new field type - EnumField
Date Tue, 13 Aug 2013 11:14:48 GMT


Erick Erickson commented on SOLR-5084:


bq: Why do you say the assumption is the type is restricted to single value?...

Parts of the discussion mentioned sorting, which is undefined on multivalued fields. If sorting
is _required_ for an enum-type field then it shouldn't be mutliValued. There's no reason it
_needs_ to be restricted to single values, it's fine for the enum type to be just like any
other field; it's up to the user to only put one value in the field if it's to be used to

Mostly getting it straight in my head what the characteristics are, not saying it _should_
be single-valued-only...

> 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