lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] [Commented] (LUCENE-6917) Move NumericField out of core to backwards-codecs
Date Thu, 10 Dec 2015 16:20:10 GMT


Uwe Schindler commented on LUCENE-6917:

I also like the legacy query to stay in core. Because the codec module should not contain
classes for public API usage. Its just a module to plug into your classpath and SPI loads
codecs from it, nothing more. No user-facing APIs. In Java 9 Jigsaw's speak it should only
export the ServiceProvider implementations but hide every implementation detail :-)

As I see in your patch, no more build.xml changes. Cool. LGTM.

> Move NumericField out of core to backwards-codecs
> -------------------------------------------------
>                 Key: LUCENE-6917
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message