[ https://issues.apache.org/jira/browse/SOLR-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810092#comment-13810092 ]
Elran Dvir commented on SOLR-5084: ---------------------------------- Attached new patch Fixes our test issues. Added "putConfig("conf1", zkClient, solrhome, "enumsConfig.xml");" in buildZooKeeper in LeaderElectionIntegrationTest. There are still test errors but I don't think it's related to our patch (thread leaked from SUITE scope at org.apache.solr.servlet.SolrRequestParserTest). Thanks. > 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, 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org