[ https://issues.apache.org/jira/browse/SOLR-11023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115108#comment-16115108 ]
ASF subversion and git services commented on SOLR-11023: -------------------------------------------------------- Commit ca0696492382e4f44d48c399986a489a82281de0 in lucene-solr's branch refs/heads/branch_7x from [~steve_rowe] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=ca06964 ] SOLR-11023: Added EnumFieldType, a non-Trie-based version of EnumField, and deprecated EnumField in favor of EnumFieldType. > Need SortedNumerics/Points version of EnumField > ----------------------------------------------- > > Key: SOLR-11023 > URL: https://issues.apache.org/jira/browse/SOLR-11023 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Reporter: Hoss Man > Assignee: Steve Rowe > Priority: Blocker > Labels: numeric-tries-to-points > Fix For: 7.0 > > Attachments: SOLR-11023.patch, SOLR-11023.patch, SOLR-11023.patch, > SOLR-11023.patch, SOLR-11023.patch, SOLR-11023.patch > > > although it's not a subclass of TrieField, EnumField does use > "LegacyIntField" to index the int value associated with each of the enum > values, in addition to using SortedSetDocValuesField when {{docValues="true" > multivalued="true"}}. > I have no idea if Points would be better/worse then Terms for low cardinality > usecases like EnumField, but either way we should think about a new variant > of EnumField that doesn't depend on > LegacyIntField/LegacyNumericUtils.intToPrefixCoded and uses > SortedNumericDocValues. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org