lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-5084) new field type - EnumField
Date Fri, 09 Aug 2013 00:09:49 GMT

    [ https://issues.apache.org/jira/browse/SOLR-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734223#comment-13734223
] 

Robert Muir commented on SOLR-5084:
-----------------------------------

{quote}
    ...nested element underneath the field type? I dont know if this is even possible or a
good idea, but its an that would remove some xml files.

i don't think the schema parsing code can handle that – it's attribute based, not nested
element based
{quote}

Right but code can change. Other parts of solr allow this kinda stuff.

{quote}
yeah ... it would be tempting to not even let the config specify numeric values – just an
ordered list, except:

1) all hell would break loose if someone accidently inserted a new element anywhere other
then the end of the list
2) you'd need/want a way to "disable" values form the middle of the list from working again.
{quote}

Well i guess i look at it differently. That this is in a sense like an analyzer. you cant
change the config without reindexing.

{quote}
I was actually thinking it would be nice to support multiple legal names (with one canonical
for respones) per value, but that would preent the simple array lookps...
{quote}

Why? I'm talking about int->canonical name (e.g. in the valuesource impl) not anything
else. as far as name->int, you want a hash anyway.
                
> 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
>         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: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message