[
https://issues.apache.org/jira/browse/LUCENE-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-7098:
-----------------------------
Fix Version/s: (was: 6.0)
master (7.0)
Manually correcting fixVersion per Step #S5 of LUCENE-7271
----
FWIW, these appear to be the key commits related to this issue...
*
https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;a=commit;h=b8cfcaf3447004447ae6b600ab4ae7dd5baf69e3
*
https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;a=commit;h=a5b941baa1aa907886760a247227ecf2cbc3eaa1
...i'm guessing something about how they were squashed prevented gitbot from
noticing them?
> BKDWriter should write ords as ints when possible during offline sort
> ---------------------------------------------------------------------
>
> Key: LUCENE-7098
> URL: https://issues.apache.org/jira/browse/LUCENE-7098
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 6.1, master (7.0)
>
> Attachments: LUCENE-7098.patch
>
>
> Today we write all ords as longs, since we support more than 2.1B values in
> one segment, but the vast majority of the time an int would suffice.
> We could look into vLong, but this quickly gets tricky because {{BKDWriter}}
> needs random access to the file and we rely on fixed-width entries to do this
> now.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
