You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Nicholas Knize (JIRA)" <ji...@apache.org> on 2015/12/14 23:19:46 UTC
[jira] [Updated] (LUCENE-6930) Decouple GeoPointField from
NumericType
[ https://issues.apache.org/jira/browse/LUCENE-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicholas Knize updated LUCENE-6930:
-----------------------------------
Description:
{{GeoPointField}} currently relies on {{NumericTokenStream}} to create prefix terms for a GeoPoint using the precision step defined in {{GeoPointField}}. At search time {{GeoPointTermsEnum}} recurses to a max precision that is computed by the Query parameters. This max precision is never the full precision, so creating and indexing the full precision terms is useless and wasteful (it was always a side effect of just using indexing logic from the Numeric type).
Furthermore, since the numerical logic always stored high precision terms first, the recursion in {{GeoPointTermsEnum}} required transient memory for storing ranges. By moving the trie logic to its own {{GeoPointTokenStream}} and reversing the term order (such that lower resolution terms are first), the GeoPointTermsEnum can naturally traverse, enabling on-demand creation of PrefixTerms. This will be done in a separate issue.
was:
{{GeoPointField}} currently relies on {{NumericTokenStream}} to create prefix terms for a GeoPoint using the precision step defined in {{GeoPointField}}. At search time {{GeoPointTermsEnum}} recurses to a max precision that is computed by the Query parameters. This max precision is never the full precision, so creating and indexing the full precision terms is useless and wasteful (it was always a side effect of just using indexing logic from the Numeric type).
Furthermore, since the numerical logic always stored high precision terms first, the recursion in {{GeoPointTermsEnum}} required transient memory for storing ranges. By moving the trie logic to its own {{GeoPointTokenStream}} and reversing the term order (such that lower resolution terms are first), the GeoPointTermsEnum can naturally traverse, enabling on-demand creation of PrefixTerms.
> Decouple GeoPointField from NumericType
> ---------------------------------------
>
> Key: LUCENE-6930
> URL: https://issues.apache.org/jira/browse/LUCENE-6930
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Nicholas Knize
>
> {{GeoPointField}} currently relies on {{NumericTokenStream}} to create prefix terms for a GeoPoint using the precision step defined in {{GeoPointField}}. At search time {{GeoPointTermsEnum}} recurses to a max precision that is computed by the Query parameters. This max precision is never the full precision, so creating and indexing the full precision terms is useless and wasteful (it was always a side effect of just using indexing logic from the Numeric type).
> Furthermore, since the numerical logic always stored high precision terms first, the recursion in {{GeoPointTermsEnum}} required transient memory for storing ranges. By moving the trie logic to its own {{GeoPointTokenStream}} and reversing the term order (such that lower resolution terms are first), the GeoPointTermsEnum can naturally traverse, enabling on-demand creation of PrefixTerms. This will be done in a separate issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org