[
https://issues.apache.org/jira/browse/SOLR-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated SOLR-5084:
---------------------------------
Attachment: Solr-5084.trunk.patch
Cleans up a couple of import statements, adds a license header etc.
Elran:
Please try running 'ant precommit' after applying the patch. That step
complains about missing JavaDocs, there are a couple of files that don't have
any.
What's the purpose of a separate trunk and 4x patch? In general we try to just
have a patch for trunk and then use the merge capability. I'm asking mostly to
see whether there are incompatibilities between trunk and 4x. If there's no
specific reason, I'll ignore the 4x patch and do the merge thing when we commit.
All:
If there are no objections, I'll probably commit this over the weekend after we
work out the precommit issues and insure that tests run, so speak up....
Erick
> 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: enumsConfig.xml, schema_example.xml, 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
