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:41:48 GMT


Hoss Man commented on SOLR-5084:

bq. but removing a legal value from the list, i think you need to reindex. Because what to
do with documents that have that integer value?

For sorting and value sources etc... nothing special happens -- they still have the same numeric
value under the covers; it's just that when writing out the "stored" values (ie: label) you
act as if they have no value in the field at all (shouldn't affect efficiency at all.)

If the user wants some other behavior the burden is on them to re-index or delete the affected
docs -- but the simple stuff stays just as simple as if they were dealing with the int<->label
mappings in their own code, the validation of legal labels just moves from the client to solr.
> 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