[
https://issues.apache.org/jira/browse/SOLR-12074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16691097#comment-16691097
]
Yonik Seeley commented on SOLR-12074:
-------------------------------------
bq. It'd be nifty if PointField could additionally have a Terms index for these
full-precision terms instead of requiring a separate field in the schema.
+1, it's important for it to be the same field in the schema for both
usability, and so that solr knows how to optimize single-valued lookups.
If we could turn back time, I'd argue for keeping "indexed=true" in the schema
to mean normal full-text index, and then use another name for the BKD structure
(rangeIndexed=true? pointIndexed=true?), but I guess that ship has sailed.
So what should the name of the new flag for the schema be?
valueIndexed?
termIndexed?
> Add numeric typed equivalents to StrField
> -----------------------------------------
>
> Key: SOLR-12074
> URL: https://issues.apache.org/jira/browse/SOLR-12074
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Schema and Analysis
> Reporter: David Smiley
> Priority: Major
> Labels: newdev, numeric-tries-to-points
>
> There ought to be numeric typed equivalents to StrField in the schema. The
> TrieField types can be configured to do this with precisionStep=0, but the
> TrieFields are deprecated and slated for removal in 8.0. PointFields may be
> adequate for some use cases but, unlike TrieField, it's not as efficient for
> simple field:value lookup queries. They probably should use the same
> internal sortable full-precision term format that TrieField uses (details
> currently in {{LegacyNumericUtils}} (which are used by the deprecated Trie
> fields).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
