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

["David Smiley (JIRA)" <ji...@apache.org>]

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

David Smiley commented on SOLR-12074:
-------------------------------------

To be clear, TrieField _at any precisionStep_ will keep a single term for each original input value.  Higher precision steps add additional terms to speed up range queries.  The task at hand in this issue is only to index those full-precision terms.  If a use-case requires range queries then the user ought to use an additional field for that to be fully optimal.

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.  For such an approach, the field type would allow the user to control what sort of indexes (Points, Terms, or both).  It should be possible (I *think* Lucene allows one field to have a Terms index & Points index) but probably more work?  Any way this path ought to be explored since it would, I think, be significantly better from an ease-of-use perspective.

> 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
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org