lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (SOLR-5084) new field type - EnumField
Date Wed, 28 Aug 2013 00:09:52 GMT


Robert Muir commented on SOLR-5084:

I still really don't think we should add an enumerated type that isn't strict about inputs
actually matching enumerated values: it loses all of its value to me.

There are a few inconsistencies where string inputs aren't mapped into their numeric value:
like ValueSourceScorer.getRangeScorer and getRangeQuery in the fieldtype (in some cases).

I don't understand the need for an analysis chain: The TrieTokenizerFactory is unnecessary
and I have a patch to remove it on some issue somewhere but just havent gotten around to committing

And I still would really like it if we didn't need a separate XML file for each enumerated
type: its like a parallel schema.xml: I think it would be much better if we could nest this
underneath the fieldtype.

Finally, I still think the ordinals should be implicit in the list (as i mentioned before).
This way the thing can actually be efficient.
> 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,
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