[
https://issues.apache.org/jira/browse/LUCENE-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046976#comment-15046976
]
Michael McCandless commented on LUCENE-6917:
--------------------------------------------
bq. I think you meant that links from "core" module that point to legacy class
won't work.
It's not that: it's a link from {{queryparser}} module to {{sandbox}} module,
and it fails because the javadocs incorrectly links the class from {{sandbox}}
as if it were in core. But talking to [~rcmuir], he seems to know what's
happening here and basically we should not be putting the same package in
multiple modules.
So ... one idea is to be less ambitious here, and instead leave NumericField in
{{core}}, but renamed to LegacyX and deprecated. Then the links will be fine
since no classes moved, they were simply renamed.
> Move NumericField out of core to backwards-codecs
> -------------------------------------------------
>
> Key: LUCENE-6917
> URL: https://issues.apache.org/jira/browse/LUCENE-6917
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 6.0
>
> Attachments: LUCENE-6917-broken-javadocs.patch, LUCENE-6917.patch,
> LUCENE-6917.patch
>
>
> DimensionalValues seems to be better across the board (indexing time,
> indexing size, search-speed, search-time heap required) than NumericField, at
> least in my testing so far.
> I think for 6.0 we should move {{IntField}}, {{LongField}}, {{FloatField}},
> {{DoubleField}} and {{NumericRangeQuery}} to {{backward-codecs}}, and rename
> with {{Legacy}} prefix?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
