You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2026/06/16 20:29:00 UTC

[jira] [Updated] (SOLR-12074) Add numeric typed equivalents to StrField

     [ https://issues.apache.org/jira/browse/SOLR-12074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Smiley updated SOLR-12074:
--------------------------------
    Labels: numeric-tries-to-points pull-request-available  (was: newdev numeric-tries-to-points pull-request-available)

> Add numeric typed equivalents to StrField
> -----------------------------------------
>
>                 Key: SOLR-12074
>                 URL: https://issues.apache.org/jira/browse/SOLR-12074
>             Project: Solr
>          Issue Type: New Feature
>          Components: Schema and Analysis
>            Reporter: David Smiley
>            Priority: Major
>              Labels: numeric-tries-to-points, pull-request-available
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> 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
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org