lucene-dev mailing list archives

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

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

Hoss Man edited comment on SOLR-5084 at 8/9/13 12:14 AM:
---------------------------------------------------------

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

i dunno ... that seems like it would really kill the utility of a field for a lot of use cases
-- if it had that kind of limitation, i would just use an "int" field an managing the mappings
myself so id always know i could add/remove (EDIT) -fields- values w/o needing to reindex.

to follow your example: if i completley change hte analyzer, then yes i have ot reindex --
but if want to stop using a ynonym, i don't have to re-index every doc, just the ones that
had that used that synonyms.

bq. as far as name->int, you want a hash anyway.

right ... never mind, i was thinking about it backwards.
                
      was (Author: hossman):
    bq. Well i guess i look at it differently. That this is in a sense like an analyzer. you
cant change the config without reindexing.

i dunno ... that seems like it would really kill the utility of a field for a lot of use cases
-- if it had that kind of limitation, i would just use an "int" field an managing the mappings
myself so id always know i could add/remove fields w/o needing to reindex.

to follow your example: if i completley change hte analyzer, then yes i have ot reindex --
but if want to stop using a ynonym, i don't have to re-index every doc, just the ones that
had that used that synonyms.

bq. as far as name->int, you want a hash anyway.

right ... never mind, i was thinking about it backwards.
                  
> 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