You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/03/20 14:15:33 UTC
[jira] [Commented] (LUCENE-7121) BKDWriter should not store ords
when documents are single valued
[ https://issues.apache.org/jira/browse/LUCENE-7121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203287#comment-15203287 ]
ASF subversion and git services commented on LUCENE-7121:
---------------------------------------------------------
Commit d392940092187ba88be0d2b0882c23800f44a74e in lucene-solr's branch refs/heads/master from Mike McCandless
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d392940 ]
LUCENE-7121: don't write ord for single-valued points, saving 4 bytes per point
> BKDWriter should not store ords when documents are single valued
> ----------------------------------------------------------------
>
> Key: LUCENE-7121
> URL: https://issues.apache.org/jira/browse/LUCENE-7121
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: master, 6.1
>
> Attachments: LUCENE-7121.patch
>
>
> Since we now have stats for points fields, it's easy to know up front whether the field you are about to build a BKD tree for is single valued or not.
> If it is single valued, we can optimize space by not storing the ordinal to identify a point, since its docID also uniquely identifies it.
> This saves 4 bytes per point, which for the 1D case is non-trivial (12 bytes down to 8 bytes per doc), and even for the 2D case is good reduction (16 bytes down to 12 bytes per doc).
> This is an optimization ... I won't push it into 6.0.
--
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